[GH-ISSUE #629] Showing https is not secure #340

New issue

Open

opened 2026-02-25 22:33:08 +03:00 by kerem · 1 comment

kerem commented

2026-02-25 22:33:08 +03:00

Owner

Originally created by @imprintnext-rajat on GitHub (Mar 28, 2025).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/629

My mkcert certificate is not working after I copied it to the PC.
It works in Firefox but not in Chrome.
Any solutions?

Originally created by @imprintnext-rajat on GitHub (Mar 28, 2025). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/629 My mkcert certificate is not working after I copied it to the PC. It works in Firefox but not in Chrome. Any solutions?

kerem commented

2026-02-25 22:33:08 +03:00

Author

Owner

@EvgeniGordeev commented on GitHub (Jul 14, 2025):

same here - works fine in firefox and safari, but not secure in chrome (latest as of today - Version 138.0.7204.101 (Official Build) (arm64))

Workaround

In my case Chrome required to serve the full chain certificate so I had to do:

cat <my_cert.pem> "$(mkcert -CAROOT)/rootCA.pem" > fullchain.pem

@EvgeniGordeev commented on GitHub (Jul 14, 2025): same here - works fine in firefox and safari, but `not secure` in chrome (latest as of today - `Version 138.0.7204.101 (Official Build) (arm64)`) ### Workaround In my case Chrome required to serve the full chain certificate so I had to do: ```shell cat <my_cert.pem> "$(mkcert -CAROOT)/rootCA.pem" > fullchain.pem ```