Replies: 3 comments 3 replies
-
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
it is working now previously i was using older image and it did used to work but recently it was giving this error and i wasnt using proxies and platform was linux and installed using docker compose as i said indirectly in my text |
Beta Was this translation helpful? Give feedback.
-
|
Everything was working fine for me until a couple of days ago when I started seeing similar errors: These are the logs from the Playwright container: I am using Docker. This is my Docker Compose file: services:
changedetection.io:
image: lscr.io/linuxserver/changedetection.io:latest
container_name: changedetection
environment:
- PUID=1000
- PGID=1000
- TZ=Asia/Kolkata
- LC_ALL=en_US.UTF-8
- BASE_URL= https://changedetection.server.io/
- PLAYWRIGHT_DRIVER_URL=ws://playwright-chrome:3000
volumes:
- /home/pi/Docker/Changedetection.io/config:/config
ports:
- 5080:5000
restart: unless-stopped
playwright-chrome:
hostname: playwright-chrome
image: dgtlmoon/sockpuppetbrowser:latest
container_name: playwright-chrome
restart: unless-stopped
tmpfs:
- /tmp # This just keeps tmp data from being written to disk
environment:
- SCREEN_WIDTH=1920
- SCREEN_HEIGHT=1024
- SCREEN_DEPTH=16
- MAX_CONCURRENT_CHROME_PROCESSES=10
- STATS_REFRESH_SECONDS=120 # Default is 3 seconds which is way too much
networks:
default:
name: changedetectionio_default
external: true |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I don't know what I did but I shut down the containers, updated the Docker Compose file: services:
changedetection.io:
image: lscr.io/linuxserver/changedetection.io:latest
container_name: changedetection
environment:
- PUID=1000
- PGID=1000
- TZ=Asia/Kolkata
- LC_ALL=en_US.UTF-8
- BASE_URL= https://changedetection.server.io/
- WEBDRIVER_URL=http://browser-chrome:4444/wd/hub
- PLAYWRIGHT_DRIVER_URL=ws://playwright-chrome:3000
volumes:
- /home/pi/Docker/Changedetection.io/config:/config
ports:
- 5080:5000
restart: unless-stopped
depends_on:
playwright-chrome:
condition: service_started
playwright-chrome:
hostname: playwright-chrome
image: dgtlmoon/sockpuppetbrowser:latest
container_name: playwright-chrome
restart: unless-stopped
tmpfs:
- /tmp # This just keeps tmp data from being written to disk
environment:
- SCREEN_WIDTH=1920
- SCREEN_HEIGHT=1024
- SCREEN_DEPTH=16
- MAX_CONCURRENT_CHROME_PROCESSES=10
- STATS_REFRESH_SECONDS=120 # Default is 3 seconds which is way too much
browser-chrome:
hostname: browser-chrome
image: selenium/standalone-chromium:latest
environment:
- VNC_NO_PASSWORD=1
- SCREEN_WIDTH=1920
- SCREEN_HEIGHT=1080
- SCREEN_DEPTH=24
volumes:
# Workaround to avoid the browser crashing inside a docker container
# See https://github.com/SeleniumHQ/docker-selenium#quick-start
- /dev/shm:/dev/shm
restart: unless-stopped
networks:
default:
name: changedetectionio_default
external: trueI started the container again and now everything is working properly again. I am unsure if its because I shut down and then started the container again or because I added Note: I am using a Raspberry Pi 4. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Had the same issue. I added the below which initially did not work but after several container restarts, it did. tmpfs: |
Beta Was this translation helpful? Give feedback.
-
|
where did you add this? was it under volumes? |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I want to change this timeout of changedetection. I thought this is timeout of browserless/chrome but this is not the case maybe ? i have doubt on this because i did set env -> CONNECTION_TIMEOUT=180000 in docker compose which i already provided so i thought that it wont create this exception issue as i am working on slow hardware tbh and so i tested with more values but in change detection it always did showed
Exception: Timeout 60000ms exceeded.So please guide if there are any env variable i can set in changedetection so that it take some more time before returning this error.
Sometimes even in logs of browserless/chrome docker container i could see logs stating that request was successful so it shouldnt have given this error but it did give that error so idk tbh what to do so please guide for this issue fix
Beta Was this translation helpful? Give feedback.
All reactions