-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Error: unable to verify the first certificate if using puppeteer_download_host #5378
Comments
What is your content of |
cat .npmrc:
cat ~/.npmrc
|
I am having same problem. Any solution to this? |
me too |
I discovered that you can configure Node SSL checks at runtime by specifying an environment variable to the node binary:
|
We're marking this issue as unconfirmed because it has not had recent activity and we weren't able to confirm it yet. It will be closed if no further activity occurs within the next 30 days. |
We are closing this issue. If the issue still persists in the latest version of Puppeteer, please reopen the issue and update the description. We will try our best to accomodate it! |
Same with current version ^19.0.0 : NODE_TLS_REJECT_UNAUTHORIZED=0 works, but it can not be a solution. |
If you are behind a corporate firewall you can set the path to a CA file including the certificates so you don't have to disable the certificate validation. $ export NODE_EXTRA_CA_CERTS=[your CA certificate file path] |
We have set up nexus proxy for caching chrome binaries.
puppeteer_download_host
is set to the desired repo (the url is reacheable by curl). Butnpm i --save-dev puppeteer
causes:Steps to reproduce
Tell us about your environment:
What steps will reproduce the problem?
Please include code that reproduces the issue.
Please note,
sass_binary_site
works nice over the same nexus, because CA certificates are already installed into system CA store.What is the expected result?
Correct download of binaries from internal nexus proxy
What happens instead?
While trying to isntall
npm i --save-dev puppeteer
i'm getting following exception:The text was updated successfully, but these errors were encountered: