[GH-ISSUE #319] Chrome has to be run at least once before mkcert notices it #203

New issue

Closed

opened 2026-02-25 22:32:51 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @JasonBarnabe on GitHub (Dec 5, 2020).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/319

If Chrome is installed but has never been run, mkcert -install doesn't install the CA to its trust store. Not really an issue on a desktop, but I was trying to get mkcert running in a CircleCI build and ran into it. If it can't be fixed, it should at least be documented:

Workaround (for CircleCI): start Chrome and kill it before running mkcert -install.

      - run:
          name: Start Chrome so that mkcert sees it
          command: |
            /opt/google/chrome/google-chrome &
            sleep 3
            killall chrome

Originally created by @JasonBarnabe on GitHub (Dec 5, 2020). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/319 If Chrome is installed but has never been run, `mkcert -install` doesn't install the CA to its trust store. Not really an issue on a desktop, but I was trying to get mkcert running in a CircleCI build and ran into it. If it can't be fixed, it should at least be documented: Workaround (for CircleCI): start Chrome and kill it before running `mkcert -install`. ``` - run: name: Start Chrome so that mkcert sees it command: | /opt/google/chrome/google-chrome & sleep 3 killall chrome ```