-
Describe the bug
Browserless/chrome / playwright itself is working because I can access it when exposing a port and a busybox container defined in the docker-compose can access it as well (with a Version To Reproduce Steps to reproduce the behavior:
! ALWAYS INCLUDE AN EXAMPLE URL WHERE IT IS POSSIBLE TO RE-CREATE THE ISSUE - USE THE 'SHARE WATCH' FEATURE AND PASTE IN THE SHARE-LINK! This works with all urls, I can't share a publicly accessible link because this is running on my LAN. Expected behavior Screenshots Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context version: '3.5'
services:
changedetection:
image: ghcr.io/dgtlmoon/changedetection.io
container_name: changedetection
hostname: changedetection
volumes:
- ./../../data/changedetection:/datastore
environment:
# Default listening port, can also be changed with the -p option
# - PORT=5000
# - PUID=1000
# - PGID=1000
#
# Alternative Playwright URL, do not use "'s or 's!
- PLAYWRIGHT_DRIVER_URL=ws://playwright-chrome:3000/
#
# Playwright proxy settings playwright_proxy_server, playwright_proxy_bypass, playwright_proxy_username, playwright_proxy_password
#
# https://playwright.dev/python/docs/api/class-browsertype#browser-type-launch-option-proxy
#
# Plain requsts - proxy support example.
# - HTTP_PROXY=socks5h://10.10.1.10:1080
# - HTTPS_PROXY=socks5h://10.10.1.10:1080
#
# An exclude list (useful for notification URLs above) can be specified by with
# - NO_PROXY="localhost,192.168.0.0/24"
#
# Base URL of your changedetection.io install (Added to the notification alert)
- BASE_URL=url
# Respect proxy_pass type settings, `proxy_set_header Host "localhost";` and `proxy_set_header X-Forwarded-Prefix /app;`
# More here https://github.com/dgtlmoon/changedetection.io/wiki/Running-changedetection.io-behind-a-reverse-proxy-sub-directory
# - USE_X_SETTINGS=1
# Comment out ports: when using behind a reverse proxy , enable networks: etc.
# ports:
# - 5000:5000
restart: unless-stopped
networks:
- reverse_proxy
- gotify
playwright-chrome:
hostname: playwright-chrome
container_name: playwright-chrome
image: browserless/chrome
restart: unless-stopped
ports:
- 1337:3000
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
busybox:
hostname: busybox
container_name: busybox
image: busybox
restart: unless-stopped
command: sleep infinity
networks:
gotify:
external:
name: gotify
reverse_proxy:
external:
name: reverse_proxy
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 7 replies
-
This is NOT a bug, this is a local configuration issue, please do not spam the issue queue
It is 100% verbose enough, it cannot hold your hand more I think
Something in your config is causing it to look at |
Beta Was this translation helpful? Give feedback.
-
converted to discussion and renamed the title of your post - please do not spam the issue queue |
Beta Was this translation helpful? Give feedback.
-
#627 The issue being that an explicit bridge network needs to be created to refer the container name (the docker-compose version might also be a factor): version: '3.5'
services:
changedetection:
...
networks:
- changedetection
...
playwright-chrome:
...
networks:
- changedetection
...
networks:
changedetection:
name: changedetection |
Beta Was this translation helpful? Give feedback.
#627
Talks about the issue.
The issue being that an explicit bridge network needs to be created to refer the container name (the docker-compose version might also be a factor):