Closed himanshu177 closed 1 year ago
@himanshu177, thank you for creating this issue. We will troubleshoot it as soon as we can.
Triage this issue by using labels.
If information is missing, add a helpful comment and then I-issue-template
label.
If the issue is a question, add the I-question
label.
If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted
label.
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable G-*
label, and it will provide the correct link and auto-close the
issue.
After troubleshooting the issue, please add the R-awaiting answer
label.
Thank you!
Duplicate #11980
Update to the latest version of Selenium.
Oops, wrong issue. We had 2 issues right next to each other without a title.
@titusfortner Hi sorry for the inconvenience, yeah they are the separate issue I have separated the issues like (-------------------2nd Output---------------------------)
No, I meant I got this issue confused the with an issue someone created right before yours... š
if I ran the same test after 5-10 minutes they are getting failed.
Before 4.13 there would be a setting in the cache that would prevent using a valid driver found on the system after a certain expiration. This was changed in 4.13, so if you upgrade you shouldn't have this particular issue.
The results you provide is just the after hook giving an error because there is no driver to use for the screenshot. If you surround your driver calls in the after hook with a try/catch, or a conditional for the driver not being null, then this message won't get in the way of the real problem. It's interesting that this is different from the error in output 2, though.
This one is straightforward, Selenium can't access the internet wit the proxy information provided. It doesn't matter if you use setHttpProxy
or setSslProxy
, we check both.
If you didn't need to set a proxy for your browser to access the internet, then setting a proxy won't help get the driver. Some people set the proxy in the driver arguments rather than with the setProxy()
method, and those are the people who need to update.
I faced no issue while accessing the URLs.
It's likely that it works through the browser, but does not work when running in the console. You can try using wget
on the links in a terminal and see. Likely your VPN is blocking it (regardless of whether you provide the proxy information). There isn't anything Selenium can do about this one, you'll need to talk to your IT department.
But, update to 4.13 and you can use the driver you downloaded when you weren't on a VPN.
@titusfortner thanks for your quick response I will definitely try with selenium 4.13.
When I deleted all the drivers from the ~.cache location and ran the test on VPN, then at that time I am getting the below error and what could be the possible reason for it?
Step failed
org.openqa.selenium.remote.NoSuchDriverException: Unable to obtain: Capabilities {browserName: chrome, goog:chromeOptions: {args: [--remote-allow-origins=*], extensions: []}}, error Command failed with code: 65, executed: [C:\Users----\AppData\Local\Temp\selenium-manager1060220119559006992931343916391560\selenium-manager.exe, --browser, chrome, --output, json]
error sending request for url (https://googlechromelabs.github.io/chrome-for-testing/known-good-versions-with-downloads.json): error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
Build info: version: '4.11.0', revision: '040bc5406b'
System info: os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '18.0.1.1'
Driver info: driver.version: ChromeDriver
at org.openqa.selenium.remote.service.DriverFinder.getPath(DriverFinder.java:25)
at org.openqa.selenium.remote.service.DriverFinder.getPath(DriverFinder.java:13)
at org.openqa.selenium.chrome.ChromeDriver.generateExecutor(ChromeDriver.java:99)
at org.openqa.selenium.chrome.ChromeDriver.
error trying to connect
Your network is not allowing Selenium access to that URL.
@titusfortner ok thank you, Also I tried to download drivers from bash using curl, so I definitely need to ask them for access.
curl https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/117.0.5938.149/win64/chromedriver-win64.zip % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:00:28 --:--:-- 0 curl: (7) Failed to connect to edgedl.me.gvt1.com port 443 after 28139 ms: Connection refused
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
What happened?
I am working for a bank, where to access the web application we need to connect to VPN, before upgrading chrome to version 117 and selenium 4.11 everything was working as expected on VPN. But after upgrading both selenium and chrome version I am unable to run the scripts because of errors that I am getting. However I also tried to access the chromedriver download links (https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/117.0.5938.149/win64/chromedriver-win64.zip) just to check whether I am able to access those URLs over the VPN or not and I faced no issue while accessing the URLs.
Observations: After running the test without connecting to VPN selenium downloads the chromedriver resources in ~.cache location and then if I connect to VPN and ran the test they are executing without any issues but if I ran the same test after 5-10 minutes they are getting failed.
So to solve the problems I also added the proxy in the code which was mentioned in one of the comment section of the bug. Also I tried to manually set the binary path for the chromeDriver but while executing the test the chrome driver is getting closed automatically with invalid session id exception.
I tried all the possible solutions which are there in the internet but no luck.
How can we reproduce the issue?
Relevant log output
Operating System
Windows 10
Selenium version
Java 4.11
What are the browser(s) and version(s) where you see this issue?
Chrome 117
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 117
Are you using Selenium Grid?
No