I am using selenium-chromedriver with Powershell to automate a website on two different Windows vurtual machines.
On one machine I get this error:
[5648:4300:0912/151844.598:ERROR:socket_manager.cc(147)] Failed to resolve address for stun.l.google.com., errorcode: -105
about 20 times in a row, every few minutes.
It doesn’t seem to affect the access to the site elements or automation at all, but fills my console.
- The host-process can resolve the above address manually.
- For simply hiding it, I tried setting the loglevel with chromeoptions but because this is an error, it still apears.
- As an actual solution, I tried adding explicit firewall rules, both on the machine itself and in Azure-NSG but no effect.
Both machines are Azure-hosted VMs, the one with the error is Win11 the other Win10.
Any ideas what could be the reason for this?
10
To summarize:
- It works on Windows 10
- It fails on Windows 11
- On Windows 11 it works when running from Powershell
Since it works in Powershell on Windows 11, it is not a Powershell version, OS or Network problem.
What is left is the selenium-chromedriver.
- Is there a different version of the driver between the machines?
- Perhaps there is a difference in defaults between Win 10 and Win 11. Could you specify which dns server should be used
9