-
Notifications
You must be signed in to change notification settings - Fork 80
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
Could not start a new session. Response code 500 #26
Comments
This seems more like an issue in Selenium, please create an issue at https://github.com/SeleniumHQ/selenium |
How it can be Selenium issue if previous driver works just fine? |
Because I think the metadata to identify browser and driver versions is changing on v115. Is that right, @mathiasbynens? |
The HTTP endpoints to figure out which browser binary maps to which driver binary are changing starting with M115+, indeed. The good news is you may not need to do any kind of version-mapping yourself anymore, since every user-facing Chrome release now comes with a Chrome for Testing binary + a ChromeDriver binary with exactly the same version. More details: https://groups.google.com/g/chromedriver-users/c/qVPTFXnedw0 |
I don't have any issue with matching Chrome version with driver version. |
Continue in SeleniumHQ/selenium#12381 |
@diemol So, this is the driver issue not Selenium |
Hi!
After driver update it can't start the browser.
Previous driver version 114.0.5735.90 works with no issue.
Chrome version - 115.0.5790.98
Chromedriver version - 115.0.5790.98
The text was updated successfully, but these errors were encountered: