-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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]: Can't start new session #1914
Comments
@mharmuth, 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! |
Please use the https://github.com/seleniumhq-community/docker-seleniarm images for ARM architecture. |
Did that. But does not help. Same error appears. To verify that I am using the arm build:
|
I missed seeing that the capabilities payload is wrong. Here is an example of a well-formed one: {
"capabilities": {
"alwaysMatch": {
"browserName": "firefox"
},
"firstMatch": [{}]
}
} |
Ah, thanks a lot. Sorry for the ticket! |
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 using the docker-compose yaml files linked in the README for for starting a simple grid (without edge). Everything starts fine and I can see/use the selenium grid and Jaeger UI.
I can even use Postman to make a GET request to http://0.0.0.0:4444/status where I get the following response:
But when I try to start a new session using the following request, I always ran into a timeout:
I tried with both browsers, and even with Behat directly. But always the same outcome. At the beginning, I had not set the
SE_SESSION_REQUEST_TIMEOUT
and the request was just running and did nothing. So I set it to 10 seconds and the after this 10 seconds I got the following response:I'm using an M1 MacBook Pro and it doesn't work with either OrbStack or DockerDesktop.
In addition I want to say, that I can't see the trace for the POST request in Jaeger UI
Command used to start Selenium Grid with Docker
Relevant log output
Operating System
macOS Ventura 13.5
Docker Selenium version (tag)
4.11.0-20230801
The text was updated successfully, but these errors were encountered: