-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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]: Augmenter fails to work with Selenium Standalone containers in Selenium 4 #14908
Comments
@srivishal1, 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! |
Can you share the container logs and the returned capabilities after starting the session? Also,
This was an old Chrome option, and it is not valid anymore.
This is what actually creates a BiDi session. |
Thanks for response. Removed options.setCapability("se:cdp", true) and options.setExperimentalOption("w3c", true); Then after running the code get the below response- Container logs- [node] [[node.driver-configuration]] Starting Selenium Grid Standalone... Capabilities returned after creating session- Capabilities: Capabilities {acceptInsecureCerts: false, browserName: chrome, browserVersion: 130.0.6723.58, chrome: {chromedriverVersion: 130.0.6723.58 (3a50e012e4c9..., userDataDir: /tmp/.org.chromium.Chromium...}, fedcm:accounts: true, goog:chromeOptions: {debuggerAddress: localhost:36227}, networkConnectionEnabled: false, pageLoadStrategy: normal, platformName: linux, proxy: Proxy(), se:cdp: ws://localhost:4444/session..., se:cdpVersion: 130.0.6723.58, se:containerName: , se:gridWebSocketUrl: ws://localhost:29149/sessio..., se:noVncPort: 7900, se:vnc: ws://localhost:4444/session..., se:vncEnabled: true, se:vncLocalAddress: ws://172.17.0.3:7900, setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webSocketUrl: ws://localhost:4444/session..., webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:extension:minPinLength: true, webauthn:extension:prf: true, webauthn:virtualAuthenticators: true} |
What happened?
When using Selenium Standalone with the Testcontainers GenericContainer for the Chrome driver, the following issue occurs when trying to use the Augmenter class to enable the BiDi protocol:
The Selenium Standalone container starts correctly, and I am able to access the WebDriver via http://localhost:4444.
However, when I attempt to augment the driver using new Augmenter().augment(driver);, the connection fails with a java.net.ConnectException, indicating that the WebDriver cannot connect to the BiDi WebSocket server, despite being able to access the same URL (http://localhost:4444) from within the container.
This issue occurs only when using Selenium Standalone and does not appear when Selenium Grid is used with the same Augmenter setup.
The connection failure does not occur when bypassing the Augmenter or using other WebDriver methods, but the BiDi functionality is unavailable in this case
How can we reproduce the issue?
Relevant log output
I tried with different versions so ignore this warning -
WARNING: Unable to find an exact match for CDP version 130, returning the closest version; found: 129; Please update to a Selenium version that supports CDP version 130
This can be reproduce with latest docker image selenium/standalone-chromium:latest or previous versions
Operating System
Mac
Selenium version
4.25 and later
What are the browser(s) and version(s) where you see this issue?
128,129,130,131
What are the browser driver(s) and version(s) where you see this issue?
128,129,130,131
Are you using Selenium Grid?
No
The text was updated successfully, but these errors were encountered: