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

Is there an issue with CDN? #451

Closed
peter-dough opened this issue Feb 22, 2024 · 11 comments
Closed

Is there an issue with CDN? #451

peter-dough opened this issue Feb 22, 2024 · 11 comments
Assignees

Comments

@peter-dough
Copy link

Just a few hours ago, I started receiving this error when installing chromedriver via npm.

Steps to Reproduce:
npm install [email protected]

Sample Error:

09:02:18  npm ERR! Current existing ChromeDriver binary is unavailable, proceeding with download and extraction.
09:02:18  npm ERR! Downloading from file:  https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/120.0.6099.109/linux64/chromedriver-linux64.zip
09:02:18  npm ERR! Error status code: 500
@scscoville
Copy link

Same issue

@mhelgerson
Copy link

mhelgerson commented Feb 22, 2024

Getting the same issues, completely blocking builds now :( trying to get 116.0.0

@peter-dough
Copy link
Author

peter-dough commented Feb 22, 2024

Came across this in the readme. I suppose this applies to >120.0.0 now? Going to try and set CHROMEDRIVER_CDNBINARIESURL=https://storage.googleapis.com/chrome-for-testing-public to see if it makes a difference.

@peter-dough
Copy link
Author

Confirming that the following worked for me. Hope this helps others.

CHROMEDRIVER_CDNBINARIESURL=https://storage.googleapis.com/chrome-for-testing-public npm install [email protected]

@scscoville
Copy link

@peter-dough
Adding this portion to .npmrc worked for me:
CHROMEDRIVER_CDNBINARIESURL=https://storage.googleapis.com/chrome-for-testing-public

@giggio giggio self-assigned this Feb 22, 2024
@giggio giggio added the bug label Feb 22, 2024
@giggio
Copy link
Owner

giggio commented Feb 22, 2024

Hey everyone, this is fixed after 121.0.1. The chrome team changed the binary url. See #448.

@peter-dough
Copy link
Author

peter-dough commented Feb 22, 2024

@giggio I believe the issue is with downloading an older version of chromedriver. Switching to a new driver doesn't resolve the original issue reported which is more of a workaround...

@giggio
Copy link
Owner

giggio commented Feb 22, 2024

@peter-dough yes, the older versions won't work anymore, as the Chromedriver team changed the urls.
I just published a new version which will use their endpoints to determine the download url, so this should not happen in the future, but we can't fix the older versions.

@yazicii
Copy link

yazicii commented Feb 28, 2024

hii @giggio I am at the latest version of the library 122.0.3 however I still got the same problem.

Error: Failed downloading chromedriver v122.0.6261.94: Download failed: server returned code 404. URL: https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/122.0.6261.94/mac-arm64/chromedriver-mac-arm64.zip, retrying ...

the url is trying to go to the edgedl and the server returns 404. I tried to change the urls with .npmrc but it did not work.

@giggio
Copy link
Owner

giggio commented Feb 28, 2024

@yazicii I just tried on Ubuntu and couldn't repro. The old URL (edgedl...) is not in the install.js file anymore, so I can't think of how it is still trying it.
Also, version 122.0.3 is tied to Chromedriver version 122.0.6261.69, not version 122.0.6261.94.
Can you send me repro steps?

Copy link

github-actions bot commented Mar 7, 2024

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants