You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dont know how easy it is to migrate to v2 Browserless V2 Migration but breaking changes dont seem to be a problem with uptime kuma, also there seems to be a new adblock feature.
Mainly open this issue to keep track of it. v1 works but is 9 month old, and running old containers is always a thing in terms of security, especially some browser things.
📝 Error Message(s) or Log
=========================== logs ===========================
<ws connecting> ws://kumachrome:3000/playwright/chromium
<ws unexpected response> ws://kumachrome:3000/playwright/chromium 428 Precondition Required
╔════════════════════════════════════════════════════╗
║ Playwright version mismatch: ║
║ - server version: v1.48 ║
║ - client version: v1.39 ║
║ ║
║ If you are using VSCode extension, restart VSCode. ║
║ ║
║ If you are connecting to a remote service, ║
║ keep your local Playwright version in sync ║
║ with the remote service version. ║
║ ║
║ <3 Playwright Team ║
╚════════════════════════════════════════════════════╝
<ws error> ws://kumachrome:3000/playwright/chromium error WebSocket was closed before the connection was established
<ws connect error> ws://kumachrome:3000/playwright/chromium WebSocket was closed before the connection was established
<ws disconnected> ws://kumachrome:3000/playwright/chromium code=1006 reason=
============================================================
🐻 Uptime-Kuma Version
2.0.0-beta.0
💻 Operating System and Arch
Docker
🌐 Browser
🖥️ Deployment Environment
Runtime: Docker version 27.3.1, build ce12230
Database: mariadb:11.5.2
Filesystem used to store the database on: cephfs
number of monitors: 96
The text was updated successfully, but these errors were encountered:
We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.
🛡️ Security Policy
📝 Describe your problem
when using browserless v2.22.0 https://github.com/browserless/browserless i get the error messega below.
dont know how easy it is to migrate to v2 Browserless V2 Migration but breaking changes dont seem to be a problem with uptime kuma, also there seems to be a new adblock feature.
Mainly open this issue to keep track of it. v1 works but is 9 month old, and running old containers is always a thing in terms of security, especially some browser things.
📝 Error Message(s) or Log
🐻 Uptime-Kuma Version
2.0.0-beta.0
💻 Operating System and Arch
Docker
🌐 Browser
🖥️ Deployment Environment
The text was updated successfully, but these errors were encountered: