[GH-ISSUE #243] Cert Authority Invalid -- Chrome & Firefox #156

New issue

Closed

opened 2026-02-25 22:32:44 +03:00 by kerem · 0 comments

kerem commented

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

Owner

Originally created by @brianqian on GitHub (Mar 14, 2020).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/243

Currently running nginx on WSL -- Ubuntu 18.04.

Installed binary on linux, configured nginx to listen on port 80 and 443.
Generated a key and certificate according to the docs
-- NET::ERR_CERT_AUTHORITY_INVALID error on Chrome and Error code: SEC_ERROR_UNKNOWN_ISSUER on Firefox
Installed mkcert executable on Windows, created a key on windows system, copied that over to CAROOT directory in linux and generated new certificates. Errors again.
Tried exporting the certificate received in the browser and importing them manually as trusted providers. As a last ditch effort tried using doing the same with the .pem file, still no luck.

example.com (redirected via hosts file) and localhost both default to http and errors occur when trying to access https://example.com and https://localhost

Ok working now. Somewhere between creating a new key again to test out a different URL, reimporting the certificates into the browser, ending the chrome process and flushing the dnscache in ipconfig it started to work. Maybe something to do with these last two steps to get it to stick but not sure.

Originally created by @brianqian on GitHub (Mar 14, 2020). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/243 Currently running nginx on WSL -- Ubuntu 18.04. - Installed binary on linux, configured nginx to listen on port 80 and 443. - Generated a key and certificate according to the docs -- NET::ERR_CERT_AUTHORITY_INVALID error on Chrome and Error code: SEC_ERROR_UNKNOWN_ISSUER on Firefox - Installed mkcert executable on Windows, created a key on windows system, copied that over to CAROOT directory in linux and generated new certificates. Errors again. - Tried exporting the certificate received in the browser and importing them manually as trusted providers. As a last ditch effort tried using doing the same with the .pem file, still no luck. example.com (redirected via hosts file) and localhost both default to http and errors occur when trying to access https://example.com and https://localhost ---------------------- Ok working now. Somewhere between creating a new key again to test out a different URL, reimporting the certificates into the browser, ending the chrome process and flushing the dnscache in ipconfig it started to work. Maybe something to do with these last two steps to get it to stick but not sure.