Playwright Driver setup on Docker/Nas

[fourofspades]

Never had any issues running the Selium webdriver, however really struggling to get the new driver working. The documentation seems more sparse.

The error I constantly get is:

WebSocket error: connect ECONNREFUSED 172.17.0.2:3000 =========================== logs =========================== <ws connecting> ws://playwright-chrome1:3000 <ws error> [object Object] <ws connect error> ws://playwright-chrome1:3000 connect ECONNREFUSED 172.17.0.2:3000 <ws disconnected> ws://playwright-chrome1:3000 code=1006 reason= ============================================================

I am using Synology NAS, and have my Playwright docker instance linked to my changedetection. I have also mapped port 3000 on the playwriight container.

Docker Setup:

[BryanWall]

I got it working by putting both containers on the same custom bridge network. I think is sometimes (or always?) required for two containers to be able to communicate with each other, depending on the environment.

This is the container that I used: https://hub.docker.com/r/browserless/chrome/

I am not using Synology, but it supports custom networks and their docs suggest that it's required for container name resolution to work.

https://kb.synology.com/en-my/DSM/help/Docker/docker_network?version=7

[fourofspades]

Interesting, I get a little further using browserless-chrome , however it appears to have trouble

TypeError: Cannot read properties of null (reading 'getBoundingClientRect') at eval (eval at evaluate (:178:30), <anonymous>:101:29) at UtilityScript.evaluate (<anonymous>:185:19) at UtilityScript.<anonymous> (<anonymous>:1:44)
It's however far more than I ever got using this image, which doesn't even connect....

https://registry.hub.docker.com/r/playwright/chrome/

It does however tell me that what I am doing is correct, with regards to container linkages, as using browserless-chrome, I can get a connection to the web driver, and clearly there is something wrong with the docker image I was using...

Problem is, there are so many Playwright docker images, which should I be using???

[dgtlmoon]

@fourofspades

1. use the :latest docker image, the getBoundingClientRect is fixed there

2. https://github.com/dgtlmoon/changedetection.io/wiki/Playwright-content-fetcher use the container mentioned there

[fourofspades]

Thanks, those two steps got me up and running..

I did notice quite a few of my watches started coming up with "Got HTML content but no text found." after updating and/or switching fetcher. Cloning and deleting the original fixed it.

[dgtlmoon]

"Got HTML content but no text found."

i've seen this when the 'filter' cant find anything useful, or the filter is no longer present in the HTML.. sometimes it needs a little delay in fetching the page.. see if you can reproduce it, I have no idea how to resolve each case tho

[soenkesmiletzki]

Shit, some problems like @fourofspades :-(
Using Synology NAS and I dont know which Image is correct.

Example: Using browserless-chrome 1.54 stable and if I enter the FETCH URL I will see a webpage with Buttons like "Search, Scrape, PDF, Screenshot" and so on.. Is this correct?

[fourofspades]

Things are working for me, however it does seem rather fragile, and works and breaks depending on docker image, and even between versions of the same docker image.

I'm using:

https://hub.docker.com/layers/chrome/browserless/chrome/1.53-chrome-stable/images/sha256-50a39d7d656483ce9f206a6178a1d59d75f8b5d86a2602a8eb084823fdfd68e7?context=explore

https://hub.docker.com/layers/changedetection.io/dgtlmoon/changedetection.io/0.39.14.1/images/sha256-f11931c7703d2dfc35a447319c2c342e18990a538539527704c6aacb97c5dd79?context=explore

Both containers are connected to the synology bridge network, and also a new network I created called changedetect.

On the browserless-chrome container, I mapped port 3000

On the changedetection container, I set the PLAYWRIGHT_DRIVER_URL to ws://browserless-chrome1:3000

Hope that helps.

[kastnerp]

Try this (replace your URL). Works for me on a Synology NAS.

version: '3.8'

services:
  changedetection.io:
    image: ghcr.io/dgtlmoon/changedetection.io
    container_name: changedetection.io
    hostname: changedetection.io
    volumes:
      - ./changedetection-data:/datastore
    environment:
      - PORT=5000
      - PUID=1000
      - PGID=1000
      - WEBDRIVER_URL=http://playwright-chrome:3000/wd/hub
      - PLAYWRIGHT_DRIVER_URL=ws://playwright-chrome:3000
      - BASE_URL=https://myurl.tld
      - HIDE_REFERER=true
    ports:
      - "5000:5000"
    restart: unless-stopped
    depends_on:
      playwright-chrome:
        condition: service_healthy

  playwright-chrome:
    hostname: playwright-chrome
    image: browserless/chrome:1.60-chrome-stable
    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
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:3000"]
      interval: 30s
      timeout: 10s
      retries: 5
      start_period: 10s

volumes:
  changedetection-data:

Note that the wiki says # If WEBDRIVER or PLAYWRIGHT are enabled, changedetection container depends on that and must wait before starting (substitute "browser-chrome" with "playwright-chrome" if last one is used)

[m0tt]

What is the BASE_URL?

[kastnerp]

You (sub)domain under which you can access the service.

[dgtlmoon]

https://github.com/dgtlmoon/changedetection.io/wiki/Synology-NAS-setup

[n1njaznutz]

Still getting OP's error when using this latest image.

WebSocket error: connect ECONNREFUSED 172.29.0.2:3000