-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
How to install Root CA to puppeteer's chromium? #219
Comments
@jedie When you say you did that workaround, you mean in your docker file, or on the host machine? |
In my own case, the workaround wasn't working, until I found out that chromium tries to open the NSS db at Since HOME=/tmp /root/bin/mkcert -install |
macbre
added a commit
to macbre/phantomas
that referenced
this issue
Jun 13, 2022
macbre
added a commit
to macbre/phantomas
that referenced
this issue
Jun 13, 2022
macbre
added a commit
to macbre/phantomas
that referenced
this issue
Jun 13, 2022
macbre
added a commit
to macbre/phantomas
that referenced
this issue
Jun 14, 2022
* Update test/ssl-certificate/generate.sh and update the tests README on how to set up mkcert * CI: install and set up mkcert (#1143) * Fix a typo * CI: remove ignore-ssl-errors flags * mkcert: make it work with puppeteer (see FiloSottile/mkcert#219) * jest: decrease thresholds as we no longer test ignore-ssl-errors flag * Container CI: run just a CLI script Instead of the entire tests suite
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A simple
mkcert -install
isn't enough to "inject" the Root CA to Chromium from puppeteer.Anybody have any good advice?
EDIT: Note: I run puppeteer in docker, maybe this is the problem. Whatever. The problem is that
~/.pki/nssdb
doesn't exist. So i came to this work-a-round:And now, the Chromium called via puppeteer can verify the ssl certificates and
'--ignore-certificate-errors'
is not needed, any more.The text was updated successfully, but these errors were encountered: