FiloSottile/mkcert

Windows: the issuer of this certificate could not be found

Open

#149 opened on Mar 14, 2019

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (58,912 stars) (3,115 forks)batch import
Windowshelp wanted

Description

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.

Contributor guide

Tech stack
go
Domain
security
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
basic certificate conceptsWindows certificate store
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate how mkcert installs the root CA on Windows (likely via certutil or PowerShell). Verify the root CA is placed in the Trusted Root Certification Authorities store. Check Edge's certificate validation logic and compare with other browsers. Look at existing comments for troubleshooting steps.