[GH-ISSUE #219] How to install Root CA to puppeteer's chromium? #143

New issue

Open

opened 2026-02-25 22:32:42 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 22:32:42 +03:00

Owner

Originally created by @jedie on GitHub (Nov 13, 2019).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/219

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:

mkdir -p $HOME/.pki/nssdb
certutil -d sql:$HOME/.pki/nssdb -N --empty-password
/root/bin/mkcert -install

And now, the Chromium called via puppeteer can verify the ssl certificates and '--ignore-certificate-errors' is not needed, any more.

Originally created by @jedie on GitHub (Nov 13, 2019). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/219 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: ``` mkdir -p $HOME/.pki/nssdb certutil -d sql:$HOME/.pki/nssdb -N --empty-password /root/bin/mkcert -install ``` And now, the Chromium called via puppeteer can verify the ssl certificates and `'--ignore-certificate-errors'` is not needed, any more.

kerem commented

2026-02-25 22:32:43 +03:00

Author

Owner

@radum commented on GitHub (Mar 18, 2021):

@jedie When you say you did that workaround, you mean in your docker file, or on the host machine?

@radum commented on GitHub (Mar 18, 2021): @jedie When you say you did that workaround, you mean in your docker file, or on the host machine?

kerem commented

2026-02-25 22:32:43 +03:00

Author

Owner

@masterzen commented on GitHub (Aug 26, 2021):

In my own case, the workaround wasn't working, until I found out that chromium tries to open the NSS db at /tmp/.pki/nssdb instead of ~/.pki/nssdb.

Since mkcert -install assumes .pki/nssdb to be anchored to $HOME it can be fixed with this modification:

HOME=/tmp /root/bin/mkcert -install

@masterzen commented on GitHub (Aug 26, 2021): In my own case, the workaround wasn't working, until I found out that chromium tries to open the NSS db at `/tmp/.pki/nssdb` instead of `~/.pki/nssdb`. Since `mkcert -install` assumes `.pki/nssdb` to be anchored to `$HOME` it can be fixed with this modification: ```sh HOME=/tmp /root/bin/mkcert -install ```