NewConnectionError('<urllib3.connection.HTTPConnection object at 0x0000019FF0C76DB0>

[hahmetcakir]

I followed the steps described in the section titled "Microsoft Windows - Running ChromeDriver natively (without Docker)." The interface doesn't display "via localhost" part in any way. Everything else seems normal. I also tried using the Chrome API but got the same error. I added the folder where ChromeDriver is located to the path, but that wasn’t enough. I copied it to every folder I could think of.

However, I keep getting this error:

Exception: HTTPConnectionPool(host='browser-chrome', port=4444): Max retries exceeded with url: /wd/hub/session (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x0000019FF0C76DB0>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))

I’m thinking there’s an issue with ChromeDriver or something is blocking it, but I have other bots that use ChromeDriver, and they work fine. However, I’m not using Chrome on top of ChromeDriver. I'm using Chromium. Chrome keeps updating itself constantly, and it won’t allow me to install an older version that is compatible with ChromeDriver.

I would think this is the issue, but why are my other bots still working?
If this is indeed the problem, how can I solve this issue of installing an older version of Chrome?

[carehart]

I hope I might be able to help you (or others reporting this error). To be clear, that error occurs simply when no webdriver has been configured (or changedetection has not been configured properly to use an implementation of one). You mention the docs for that, and I'll clarify for readers that the URL is here.

I realize you say you followed the steps there for the Windows install of that driver. It would seem you may have missed a step. Let's consider a couple of possibilities.

1. First, when you say, "The interface doesn't display "via localhost" part in any way", are you confirming that by looking at the general settings page--rather than the settings for a given detection url? More specifically, are you clicking Settings on the top nav bar, then choosing "Fetching", to see what's shown for the "Fetch Method" of WebDriver? (See a picture at the doc page you mentioned.)

I only press this point because if instead you may have been looking instead at the line in the settings for a given detection (under its "Request" menu and then its "Fetch method" setting), I don't find that changes to depict the URL used for the driver.

2. Next, as you may recall from that docs page, the value you would see (in that general settings page, such as at http://localhost:5000/settings#fetching) would be any that you had set as an environment variable before starting up changedetection.

And in the "Windows" section of that page, it shows using a set WEBDRIVER_URL command, and THAT example shows pointing it to a localhost implementation. Did you do that?

3. Then again, you mention "I added the folder where ChromeDriver is located to the path, but that wasn’t enough. I copied it to every folder I could think of." I'm not sure that was your problem. The driver (when running) is set to listen on a port (thus the URL discussed above). Again, THAT is what you need to point to (and of course, it has to be running.)

Of course, it does have to be running. The doc page shows running the downloaded chromedriver.exe, as found in the Windows temp folder for the user who took the screenshot, as this seems to be where their browser saved such a downloaded file. You might have saved yours to a downloads folder, etc. And note how the screenshot also shows it reporting that it was indeed now "starting...on port 9515". Did you see such a message?

4. Finally, note the docs page indicates setting the env var (with the SET command) and then it says to "Run the app from the same window using the changedetection.py." By default, such a SET command only creates an env var in the given command prompt where it was entered, which is why the doc suggests then running the changedetection app from that same window. Did you do that?

You'd need to repeat the steps above each time you wanted to run changedetect, of course. (That said, it is possible to set env vars permanently on Windows using SETX instead, at least when running a command prompt as admin.)

5. In conclusion, I'll note that I was getting this exact error you describe--at least until I too found this page and performed those steps. In my case, I was using the container approach for both changedetection and the listed selenium/standalone-chrome-debug implementation of the webdriver. (Those doing that would instead find the UI pointing to http://selenium:4444/wd/hub--as is indicated also on that page, in the setting of the -e WEBDRIVER_URL value in the docker run command starting changedetection.)

Once I did those couple of steps then the detections which failed (when I chose to use the "fetch method" of "WebDriver Chrome/Javascript") now worked. I no longer got the error you got: so I really think the solution is just about getting that correctly configured for your setup.

Hope that helps (or maybe it may help future readers finding this discussion).