[GH-ISSUE #149] Windows: the issuer of this certificate could not be found #93

New issue

Open

opened 2026-02-25 22:32:35 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @binarykitchen on GitHub (Mar 14, 2019).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/149

This comes up when you open the certificate mkcert has generated for you. Under the tab "Certification Path" under "Certificate Status".

I've already run mkcert -install in Windows Powershell so the issuer itself should be trusted and known.

Also Edge says certificate is invalid when I use it for local development hmmm.

Originally created by @binarykitchen on GitHub (Mar 14, 2019). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/149 This comes up when you open the certificate mkcert has generated for you. Under the tab "Certification Path" under "Certificate Status". I've already run `mkcert -install` in Windows Powershell so the issuer itself should be trusted and known. Also Edge says certificate is invalid when I use it for local development hmmm.

kerem added the

help wanted

Windows

labels

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

kerem commented

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

Author

Owner

@FiloSottile commented on GitHub (Jun 1, 2019):

Can you try mkcert -uninstall and mkcert -install? And if that doesn't work, trying it again from an Administrator terminal?

@FiloSottile commented on GitHub (Jun 1, 2019): Can you try `mkcert -uninstall` and `mkcert -install`? And if that doesn't work, trying it again from an Administrator terminal?

kerem commented

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

Author

Owner

@gillesosx commented on GitHub (Dec 8, 2020):

Hi,

I have an issue much the same as the one described here. The certificate has been created on a Mac computer, and to test on a Windows computer I copied rootCA-key.pem from the Mac to the Windows computer, When I want to access the site, that is brought up by http-server I am told this is not trusted.

The user accounts are different on the computers. What should I do to have my setup working ?

Thanks

@gillesosx commented on GitHub (Dec 8, 2020): Hi, I have an issue much the same as the one described here. The certificate has been created on a Mac computer, and to test on a Windows computer I copied rootCA-key.pem from the Mac to the Windows computer, When I want to access the _site_, that is brought up by http-server I am told this is not trusted. ![image](https://user-images.githubusercontent.com/20879100/101509601-ee185c80-3946-11eb-9aa9-449e7b54d7e7.png) ![image](https://user-images.githubusercontent.com/20879100/101509867-36d01580-3947-11eb-9669-ebb554571fd0.png) The user accounts are different on the computers. What should I do to have my setup working ? Thanks

kerem commented

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

Author

Owner

@euphbriggs commented on GitHub (May 7, 2021):

I'm experiencing this same issue. I'm hoping to use mkcert for a microservice that is only available on our internal company network. My plan was to install mkcert and run mkcert -install on the machines that are authorized to access the microservice. Is this outside the supported use cases for mkcert?

@euphbriggs commented on GitHub (May 7, 2021): I'm experiencing this same issue. I'm hoping to use mkcert for a microservice that is only available on our internal company network. My plan was to install mkcert and run `mkcert -install` on the machines that are authorized to access the microservice. Is this outside the supported use cases for mkcert?

kerem referenced this issue

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

[PR #93] [CLOSED] Add support for building snaps #389