Seleniarm Webdriver doesn't work

[shokwaav]

Describe the bug
I can't get the webdriver to work on my Raspberry Pi.

Version
0.39.11

To Reproduce
I've installed changedetection.io and seleniarm via docker.

docker run -d \
  --name selenium \
  --restart unless-stopped \
  -p 4444:4444 \
  --shm-size="2g" \
  seleniarm/standalone-chromium:4.0.0-20211213
  
docker run -d \
  --name changedetection.io \
  --restart unless-stopped \
  --link selenium \
  -p 5000:5000 \
  -e WEBDRIVER_URL="http://localhost:4444" \
  -v datastore-volume:/datastore \
  dgtlmoon/changedetection.io

I can access both changedetection.io and seleniarm via the IP:5000 and IP:4444 respectively.

However I am still getting the following error:

Content fetcher 'html_webdriver' did not respond.
Be sure that the selenium/webdriver runner is running and accessible via network from this container/host.
Did you follow the instructions in the wiki?

WebDriver Host: http://localhost:4444
[Go here for more information](https://github.com/dgtlmoon/changedetection.io/wiki/Fetching-pages-with-WebDriver)
Content fetcher did not respond properly, unable to use it. HTTPConnectionPool(host='localhost', port=4444): Max retries exceeded with url: /session (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] ECONNREFUSED'))

As you can see I have already changed the URL for the webdriver to http://localhost:4444 as mentioned here on stackoverflow due to changes in Selenium 4, but there's still no change.

Expected behavior
I expect changedetection.io to work with the Selenium 4 webserver.

Desktop (please complete the following information):

• Raspbian 64 bit lite.

Thanks for any help I can get in advance!

[dgtlmoon]

@shokwaav in the configuration, replace WebDriver Host: http://localhost:4444 with WebDriver Host: http://selenium:4444

did that help? if not, paste the errors again

[shokwaav]

That worked thanks!

I also ended up trying 172.17.0.2:4444 too (the IP it showed on the selenium UI) and it also worked.

[dgtlmoon]

Yup sorry, there was a bug in the wiki docs, which I just fixed :)