-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐛 Bug]: Setting a Proxy when using RemoteWebdriver does not start the session #12475
Comments
@tslape, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
Why do you need to set a proxy for a remote browser? |
After a settings or network change on our workstations, running one test while on the VPN would take an extra 20 seconds for the initial load of the site. The issue was resolved by adding the AutoDetect proxy. |
Another use case: We use a proxy during our automated tests to fake server responses or track/assert browser requests. |
I'm also getting this issue- when setting proxy. When removing the proxy config it works: Error: |
I'm also stuck with this issue.
|
I also have the same issue.
|
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?
When attempting to run a test using using selenium-server-4.11.0.jar to start a standalone server and using a proxy with RemoteWebdriver, the session is never started. It cannot cast class java.util.LinkedHashMap to org.openqa.selenium.Proxy
Using a proxy with Chromedriver does not see an issue. Starting the server with the previous version, selenium-server-4.10.0.jar, does not see any issues with the proxy and RemoteWebdriver. The issue persists even when specifying the JDK client 4.11.0 to start the server.
How can we reproduce the issue?
Relevant log output
Operating System
Windows 11, Windows 10
Selenium version
Dotnet 4.11.0, JavaScript 4.11.1
What are the browser(s) and version(s) where you see this issue?
Chrome 115
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver Stable 115.0.5790.102
Are you using Selenium Grid?
4.11.0 with Java 17.0.8
The text was updated successfully, but these errors were encountered: