connection with sockpuppetbrowser is failing

[vaibhavjain-zluri]

Describe the bug
We are watching close to 500 URL's, the main service and socpuppetbrowser both has 1.5m cpu and 1.5gb memory.

1. The connection with sockpuppetbrowser is failing with this error
   Exception: BrowserType.connect_over_cdp: WebSocket error: connect ECONNREFUSED 172.20.241.113:80 Call log: <ws connecting> ws://sockpuppetbrowser/ - <ws error> ws://sockpuppetbrowser/ error connect ECONNREFUSED 172.20.241.113:80 - <ws connect error> ws://sockpuppetbrowser/ connect ECONNREFUSED 172.20.241.113:80 - <ws disconnected> ws://sockpuppetbrowser/ code=1006 reason=

2. When the above happens for sometime, the queue-size get stuck and doesn't pick up next tasks. I'm assuming it gets stuck somewhere in the state management.

I have checked its not limiting on resources. what could be the possible reason?

Version
0.50.7

How did you install?
Docker

[pdafoto]

I have a similar problem, I get this error on all my URL's watched with sockpuppetbrowser, it started 3 days ago:
Exception: BrowserType.connect_over_cdp: Timeout 60000ms exceeded. Call log: <ws connecting> ws://sockpuppetbrowser:3000/ - <ws connected> ws://sockpuppetbrowser:3000/

v0.50.8 on Docker

[dgtlmoon]

are you using our docker-compose.yml ?

[vaibhavjain-zluri]

yes, we are using docker-compose.yml. Attaching the file here:

services:
  changedetection:
    build: .
    container_name: changedetection
    hostname: changedetection
    volumes:
      - ./data:/datastore
    environment:
      - PLAYWRIGHT_DRIVER_URL=ws://sockpuppetbrowser:3000
    ports:
      - 5000:5000
    restart: unless-stopped

  sockpuppetbrowser:
    hostname: sockpuppetbrowser
    image: dgtlmoon/sockpuppetbrowser:latest
    cap_add:
      - SYS_ADMIN

[pdafoto]

Here's mine:

services:
  changedetection:
    container_name: ChangeDetection
    image: dgtlmoon/changedetection.io
    security_opt:
      - no-new-privileges:true
    restart: on-failure:5
    healthcheck:
      test: timeout 10s bash -c ':> /dev/tcp/127.0.0.1/5000' || exit 1
      interval: 10s
      timeout: 5s
      retries: 3
      start_period: 90s
    ports:
      - 5054:5000
    volumes:
      - /volume2/docker/changedetection:/datastore:rw
    depends_on:
     sockpuppetbrowser:
      condition: service_started
    environment:
      TZ: Europe/Madrid
      PLAYWRIGHT_DRIVER_URL: ws://sockpuppetbrowser:3000
     
  sockpuppetbrowser:
    container_name: ChangeDetection-SOCK
    image: dgtlmoon/sockpuppetbrowser:latest
    cap_add:
     - SYS_ADMIN
    restart: on-failure:5

[wiggum55]

I'm also having the same issue on all of my monitored URL's since an update to ChangeDetection-SOCK on 6th August.

[chiragkrishna]

running on latest: 0.50.9
same here none of my watch lists work, the webui shows Exception: BrowserType.connect_over_cdp:

Exception: BrowserType.connect_over_cdp: Timeout 60000ms exceeded. Call log: <ws connecting> ws://browser-sockpuppet-chrome:3000/ - <ws connected> ws://browser-sockpuppet-chrome:3000/

notification works but logs have CRITICAL: Failed to get notification:

2025-08-18 18:31:50.858 | CRITICAL | changedetectionio.queue_handlers:get:389 - CRITICAL: Failed to get notification: 
2025-08-18 18:31:51.151 | ERROR    | changedetectionio.async_update_worker:async_update_worker:292 - Worker 4 exception processing watch UUID: 72b015af-ef68-44ab-bf00-89c3a67e4625
2025-08-18 18:31:51.151 | ERROR    | changedetectionio.async_update_worker:async_update_worker:293 - BrowserType.connect_over_cdp: Timeout 60000ms exceeded.
<ws connecting> ws://browser-sockpuppet-chrome:3000/
  - <ws connected> ws://browser-sockpuppet-chrome:3000/
2025-08-18 18:31:51.173 | ERROR    | changedetectionio.async_update_worker:async_update_worker:292 - Worker 8 exception processing watch UUID: d8b4bfaa-41e0-4ec9-8cce-c61d70b0b955
2025-08-18 18:31:51.173 | ERROR    | changedetectionio.async_update_worker:async_update_worker:293 - BrowserType.connect_over_cdp: Timeout 60000ms exceeded.
<ws connecting> ws://browser-sockpuppet-chrome:3000/
  - <ws connected> ws://browser-sockpuppet-chrome:3000/
2025-08-18 18:31:51.176 | ERROR    | changedetectionio.async_update_worker:async_update_worker:292 - Worker 1 exception processing watch UUID: 7a001cd4-baec-4979-9e31-1e52a1ba50fe
2025-08-18 18:31:51.176 | ERROR    | changedetectionio.async_update_worker:async_update_worker:293 - BrowserType.connect_over_cdp: Timeout 60000ms exceeded.
<ws connecting> ws://browser-sockpuppet-chrome:3000/
  - <ws connected> ws://browser-sockpuppet-chrome:3000/
2025-08-18 18:31:51.181 | ERROR    | changedetectionio.async_update_worker:async_update_worker:292 - Worker 5 exception processing watch UUID: a67f7776-06f1-4ea7-ab7a-86aa378b2e27
2025-08-18 18:31:51.181 | ERROR    | changedetectionio.async_update_worker:async_update_worker:293 - BrowserType.connect_over_cdp: Timeout 60000ms exceeded.
<ws connecting> ws://browser-sockpuppet-chrome:3000/
  - <ws connected> ws://browser-sockpuppet-chrome:3000/
2025-08-18 18:31:51.188 | ERROR    | changedetectionio.async_update_worker:async_update_worker:292 - Worker 3 exception processing watch UUID: de1be030-2f55-438a-beca-78d6fa6d555b
2025-08-18 18:31:51.188 | ERROR    | changedetectionio.async_update_worker:async_update_worker:293 - BrowserType.connect_over_cdp: Timeout 60000ms exceeded.
<ws connecting> ws://browser-sockpuppet-chrome:3000/
  - <ws connected> ws://browser-sockpuppet-chrome:3000/
2025-08-18 18:31:51.191 | ERROR    | changedetectionio.async_update_worker:async_update_worker:292 - Worker 0 exception processing watch UUID: 4f2451b3-04b1-483d-9a53-f7f2b6705ae0
2025-08-18 18:31:51.191 | ERROR    | changedetectionio.async_update_worker:async_update_worker:293 - BrowserType.connect_over_cdp: Timeout 60000ms exceeded.
<ws connecting> ws://browser-sockpuppet-chrome:3000/
  - <ws connected> ws://browser-sockpuppet-chrome:3000/
2025-08-18 18:31:51.194 | ERROR    | changedetectionio.async_update_worker:async_update_worker:292 - Worker 9 exception processing watch UUID: 8118ead9-8d67-4572-b453-80d057bbb919
2025-08-18 18:31:51.194 | ERROR    | changedetectionio.async_update_worker:async_update_worker:293 - BrowserType.connect_over_cdp: Timeout 60000ms exceeded.
<ws connecting> ws://browser-sockpuppet-chrome:3000/
  - <ws connected> ws://browser-sockpuppet-chrome:3000/
2025-08-18 18:31:51.198 | ERROR    | changedetectionio.async_update_worker:async_update_worker:292 - Worker 6 exception processing watch UUID: e44d49f6-6e9d-4ec6-b334-c9b1c9f524e4
2025-08-18 18:31:51.198 | ERROR    | changedetectionio.async_update_worker:async_update_worker:293 - BrowserType.connect_over_cdp: Timeout 60000ms exceeded.
<ws connecting> ws://browser-sockpuppet-chrome:3000/
  - <ws connected> ws://browser-sockpuppet-chrome:3000/
2025-08-18 18:31:51.202 | ERROR    | changedetectionio.async_update_worker:async_update_worker:292 - Worker 2 exception processing watch UUID: c3daad47-ba5b-4d9f-890a-f9e64f82b2ad

2025-08-18 18:31:51.202 | ERROR    | changedetectionio.async_update_worker:async_update_worker:293 - BrowserType.connect_over_cdp: Timeout 60000ms exceeded.
<ws connecting> ws://browser-sockpuppet-chrome:3000/
  - <ws connected> ws://browser-sockpuppet-chrome:3000/
2025-08-18 18:31:51.234 | ERROR    | changedetectionio.async_update_worker:async_update_worker:292 - Worker 7 exception processing watch UUID: ee146751-9b13-492e-977f-8a305c9a900a
2025-08-18 18:31:51.234 | ERROR    | changedetectionio.async_update_worker:async_update_worker:293 - BrowserType.connect_over_cdp: Timeout 60000ms exceeded.
<ws connecting> ws://browser-sockpuppet-chrome:3000/
  - <ws connected> ws://browser-sockpuppet-chrome:3000/
2025-08-18 18:31:51.858 | CRITICAL | changedetectionio.queue_handlers:get:389 - CRITICAL: Failed to get notification: 
2025-08-18 18:31:52.858 | CRITICAL | changedetectionio.queue_handlers:get:389 - CRITICAL: Failed to get notification: 
2025-08-18 18:31:53.859 | CRITICAL | changedetectionio.queue_handlers:get:389 - CRITICAL: Failed to get notification: 
2025-08-18 18:31:54.860 | CRITICAL | changedetectionio.queue_handlers:get:389 - CRITICAL: Failed to get notification: 

[dgtlmoon]

not enough info, can you paste the whole output of docker ps ?

[chiragkrishna]

logs are spammed by

CRITICAL | changedetectionio.queue_handlers:get:389 - CRITICAL: Failed to get notification: 

anyways here are the fresh logs after force recreate
_changedetection_logs.txt
_changedetection-playwright-chrome_logs.txt

CONTAINER ID                                                       IMAGE                                        COMMAND                                       CREATED         STATUS                   PORTS      NAMES
fac93881728aa5c8f09dd455908bb23b3abe9a2d869c35363e5f3e22d90c1cc5   ghcr.io/dgtlmoon/changedetection.io:latest   "python ./changedetection.py -d /datastore"   8 minutes ago   Up 8 minutes (healthy)   5000/tcp   changedetection
167f905e4825ee8d2c39f272731a7914ffcb5ece0d530a8dfb26f696f8072d7d   dgtlmoon/sockpuppetbrowser:latest            "tini -- /usr/local/bin/entrypoint.sh"        8 minutes ago   Up 8 minutes (healthy)              changedetection-playwright-chrome

[dgtlmoon]

its pretty obvious, you are doing something custom changedetection-playwright-chrome is not in our original docker compose YML, please recheck it, you are using some custom name which is not the right one that matches hostname:

[chiragkrishna]

its pretty obvious, you are doing something custom changedetection-playwright-chrome is not in our original docker compose YML, please recheck it, you are using some custom name which is not the right one that matches hostname:

ive been using it like that from years,... anyways here is what i found out, hitting the recheck all fails. but if recheck individual sites, it works

=====================================
Solved
It was my Elasticsearch hogging up my RAM, which was killing playwright workers silently

[thickconfusion]

@dgtlmoon I am having this issue too. here is my docker-compose:

services:
  changedetection:
    image: ghcr.io/dgtlmoon/changedetection.io
    container_name: changedetection
    hostname: changedetection
    environment:
      - PORT=5000
      - PUID=1000
      - PGID=1000
      - PLAYWRIGHT_DRIVER_URL=ws://sockpuppetbrowser:3000
    volumes:
      - ./datastore-volume:/config
    ports:
      - 5000:5000
    restart: unless-stopped
    depends_on:
      sockpuppetbrowser:
        condition: service_started

  sockpuppetbrowser:
    image: dgtlmoon/sockpuppetbrowser:latest
    hostname: sockpuppetbrowser
    restart: unless-stopped
    environment:
      - SCREEN_WIDTH=1920
      - SCREEN_HEIGHT=1024
      - SCREEN_DEPTH=16
      - ENABLE_DEBUGGER=false
      - PREBOOT_CHROME=true
      - CONNECTION_TIMEOUT=300000
      - MAX_CONCURRENT_SESSIONS=10
      - CHROME_REFRESH_TIME=600000
      - DEFAULT_BLOCK_ADS=true
      - DEFAULT_STEALTH=true
      - DEFAULT_IGNORE_HTTPS_ERRORS=true

[dgtlmoon]

@thickconfusion you didnt supply any more information, no logs from the containers, i cant do much

you are also using a very custom docker-compose.yml

[thickconfusion]

@dgtlmoon Here are the relevant logs after setting to TRACE.

sockpuppetbrowser-1  | 2025-08-18 17:05:12.963 | INFO     | __main__:stats_thread_func:704 - Connections: Active count 0 of max 10, Total processed: 0                        .
sockpuppetbrowser-1  | 2025-08-18 17:05:12.964 | INFO     | __main__:stats_thread_func:727 - Process info: 0 child processes
changedetection      | 2025-08-18 13:05:13.849 | CRITICAL | changedetectionio.queue_handlers:get:389 - CRITICAL: Failed to get notification:
changedetection      | 2025-08-18 13:05:13.853 | TRACE    | changedetectionio.flask_app:ticker_thread_check_time_launch_checks:794 - b072e696-bca4-41ae-95af-758dd4ff8302 Time scheduler - Using system/global settings
changedetection      | 2025-08-18 13:05:13.853 | TRACE    | changedetectionio.flask_app:ticker_thread_check_time_launch_checks:794 - b8a50727-ae4e-4824-9d96-4a0b8774a3c9 Time scheduler - Using system/global settings
changedetection      | 2025-08-18 13:05:14.849 | CRITICAL | changedetectionio.queue_handlers:get:389 - CRITICAL: Failed to get notification:
changedetection      | 2025-08-18 13:05:15.850 | CRITICAL | changedetectionio.queue_handlers:get:389 - CRITICAL: Failed to get notification:
changedetection      | 2025-08-18 13:05:15.853 | TRACE    | changedetectionio.flask_app:ticker_thread_check_time_launch_checks:794 - b072e696-bca4-41ae-95af-758dd4ff8302 Time scheduler - Using system/global settings
changedetection      | 2025-08-18 13:05:15.854 | TRACE    | changedetectionio.flask_app:ticker_thread_check_time_launch_checks:794 - b8a50727-ae4e-4824-9d96-4a0b8774a3c9 Time scheduler - Using system/global settings

Please note that regarding the docker-compose, I have reviewed the repo's docker compose and have tried to produce something that is functional and logically named as I had a lot of issues getting it to work but has been working for the last year until I pulled new images today.

Here is my docker ps

fc9c064a9e89   ghcr.io/dgtlmoon/changedetection.io          "python ./changedete…"   4 minutes ago   Up 4 minutes            0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp                                                changedetection
080116e657ad   dgtlmoon/sockpuppetbrowser:latest            "tini -- /usr/local/…"   4 minutes ago   Up 4 minutes                                                                                                       changedetection-sockpuppetbrowser-1

[huyz]

I don't have anything to add except that upgrading to latest gave me all the same CRITICAL: Failed to get notification: and rolling back to 0.50.8 got logs back to normal.