Skip to content
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

Closed
gtach2o opened this issue Jul 19, 2023 · 7 comments
Closed

Could not start a new session. Response code 500 #26

gtach2o opened this issue Jul 19, 2023 · 7 comments

Comments

@gtach2o
Copy link

gtach2o commented Jul 19, 2023

Hi!
After driver update it can't start the browser.
Previous driver version 114.0.5735.90 works with no issue.

	Suppressed: org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Response code 500. Message: unknown error: cannot find Chrome binary 
Build info: version: '4.10.0', revision: 'c14d967899'
System info: os.name: 'Mac OS X', os.arch: 'aarch64', os.version: '13.4.1', java.version: '20.0.1'

Chrome version - 115.0.5790.98
Chromedriver version - 115.0.5790.98

@diemol
Copy link

diemol commented Jul 19, 2023

This seems more like an issue in Selenium, please create an issue at https://github.com/SeleniumHQ/selenium

@gtach2o
Copy link
Author

gtach2o commented Jul 19, 2023

How it can be Selenium issue if previous driver works just fine?

@diemol
Copy link

diemol commented Jul 19, 2023

Because I think the metadata to identify browser and driver versions is changing on v115. Is that right, @mathiasbynens?

@mathiasbynens
Copy link
Member

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

@gtach2o
Copy link
Author

gtach2o commented Jul 19, 2023

I don't have any issue with matching Chrome version with driver version.
What I'm saying is driver 115.0.5790.98 is not able to start Chrome browser 115.0.5790.98

@gtach2o
Copy link
Author

gtach2o commented Jul 19, 2023

Continue in SeleniumHQ/selenium#12381

@gtach2o gtach2o closed this as completed Jul 19, 2023
@gtach2o
Copy link
Author

gtach2o commented Jul 20, 2023

@diemol So, this is the driver issue not Selenium
#30 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants