Closed Jobvdb closed 3 days ago
@Jobvdb, 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!
Thanks for reporting, the bindings need to pass along the proxy information to Selenium Manager only when things need to be routed through a host instead of always,
Thanks for picking this up! In the meantime, is there a work-around for this, except for not using the proxy setting?
Looks like it was added back in 4.9, which is too far back to make sense to downgrade versions.
Can either remove proxy or manage the drivers yourself for now.
Alright, that was what I was going for, except I’m currently running 4.18.1 and it is working on that version. Not sure if that helps?
Oh, that's interesting. Can you turn on debugging and see what's different between the two? https://www.selenium.dev/documentation/webdriver/troubleshooting/logging/
Added Logger, but it seems to not log anything at all, before throwing the NoSuchDriverException
. Maybe I'm doing it wrong? Here is my updated code:
@Test
void withProxy() {
Logger logger = Logger.getLogger("Proxy logger");
logger.setLevel(Level.FINEST);
Arrays.stream(logger.getHandlers()).forEach(handler -> {
handler.setLevel(Level.FINEST);
});
org.openqa.selenium.Proxy proxy = new org.openqa.selenium.Proxy();
proxy.setProxyType(org.openqa.selenium.Proxy.ProxyType.DIRECT);
ChromeOptions chromeOptions = new ChromeOptions();
chromeOptions.setProxy(proxy);
}
You can try this tomorrow after the Nightly build has been generated. This will be also part of the 4.23 release.
Perfect thanks! Tested and it works with the 4.23.0-SNAPSHOT
version
What happened?
Im developing a test automation app that uses Selenium and with upgrading from 4.18.1 to 4.21.0, I got this error: Unable to obtain: chromedriver, error Command failed with code: 2, executed: [--browser, chrome, --proxy, --language-binding, java, --output, json] error: a value is required for '--proxy' but none was supplied For more information, try '--help'.
In the example below, I'm using ProxyType.DIRECT, but any type will trigger this behavior (including AUTODETECT)
How can we reproduce the issue?
Relevant log output
Operating System
macOS
Selenium version
Java 4.21.0
What are the browser(s) and version(s) where you see this issue?
Chrome 126.0.6478.62 (Official build) (arm64)
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 126.0.6478.62
Are you using Selenium Grid?
No response