-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
[🐛 Bug]: UnreachableBrowserException: Error communicating with the remote browser. It may have died. #2840
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
Comments
@prajaktak15, 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 unmount this volume? Or a specific cert in another dir, not $HOME |
Hello, We are trying the given solution. Will share you results. |
Hello, We tried the given solution, getting same error. code snippet to create RemoteWebDriver with all browser : private void setBrowserCapabilities(MutableCapabilities capabilities) { Please let us know if you need more details. Thank you. |
Uh oh!
There was an error while loading. Please reload this page.
What happened?
We are facing issue while executing serenity tests in selenium grid. Serenity version is v4.2.16 .
Tests are failing with below error intermittently.
UnreachableBrowserException: Error communicating with the remote browser. It may have died.
Experiencing issue with selenium version v4.28 onwards for both platforms Linux and Windows.
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Operating System
Linux Redhat
Docker Selenium version (image tag)
4.30.0-20250323
Selenium Grid chart version (chart version)
No response
The text was updated successfully, but these errors were encountered: