[GH-ISSUE #557] Basic commands don't work on macOS after brew install (mkcert -install, -CAROOT responds with "unknown option") #329

New issue

Closed

opened 2026-02-25 22:33:07 +03:00 by kerem · 4 comments

kerem commented

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

Owner

Originally created by @kopeboy on GitHub (Nov 15, 2023).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/557

Environment

Operating system (including version): macOS Ventura 13.5.2
mkcert version (from mkcert -version): 3.2.0
Server (where the certificate is loaded): local
Client (e.g. browser, CLI tool, or script): any

What you did

brew uninstall --ignore-dependencies mkcert => ok
brew install mkcert => ok
mkcert -install => error: unknown option
mkcert -CAROOT => error: unknown option

What went wrong

I don't know. Maybe multiple copies of go on my machine, or an installation in a non-canonical location, or a problem with the homebrew script? I had installed mkcert in a local node.js app so maybe it conflicted? I have removed it and reinstalled from brew but still getting unknown option errors..

Originally created by @kopeboy on GitHub (Nov 15, 2023). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/557 ## Environment * Operating system (including version): macOS Ventura 13.5.2 * mkcert version (from `mkcert -version`): 3.2.0 * Server (where the certificate is loaded): local * Client (e.g. browser, CLI tool, or script): any ## What you did 1. brew uninstall --ignore-dependencies mkcert => ok 2. brew install mkcert => ok 3. mkcert -install => **error: unknown option** 4. mkcert -CAROOT => **error: unknown option** ## What went wrong I don't know. Maybe multiple copies of go on my machine, or an installation in a non-canonical location, or a problem with the homebrew script? I had installed mkcert in a local node.js app so maybe it conflicted? I have removed it and reinstalled from brew but still getting unknown option errors..

kerem closed this issue

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

kerem commented

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

Author

Owner

@kopeboy commented on GitHub (Nov 15, 2023):

Also, is it normal that mkcert --help output doesn't contain the important -install option!?

Usage: mkcert [options] [command]

Options:
  -V, --version                             output the version number
  -h, --help                                display help for command

Commands:
  create-ca [options]
  create-cert|create-certificate [options]
  help [command]                            display help for command

@kopeboy commented on GitHub (Nov 15, 2023): Also, is it normal that **mkcert --help** output doesn't contain the important -install option!? ``` Usage: mkcert [options] [command] Options: -V, --version output the version number -h, --help display help for command Commands: create-ca [options] create-cert|create-certificate [options] help [command] display help for command ```

kerem commented

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

Author

Owner

@kopeboy commented on GitHub (Nov 15, 2023):

I have 466 certificates on my machine, I don't even know where to start 😅

@kopeboy commented on GitHub (Nov 15, 2023): I have 466 certificates on my machine, I don't even know where to start 😅 ![image](https://github.com/FiloSottile/mkcert/assets/4728367/8489194b-4cb6-4ffd-b603-ef8bca55e5e3)

kerem commented

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

Author

Owner

@rfay commented on GitHub (Nov 15, 2023):

Your mkcert is not the mkcert from this project. You should close this issue and install the mkcert from this project, thanks!

@rfay commented on GitHub (Nov 15, 2023): Your mkcert is not the mkcert from this project. You should close this issue and install the mkcert from this project, thanks!

kerem commented

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

Author

Owner

@ctrl-alter-ego commented on GitHub (Apr 12, 2024):

I also had this problem (yes, with this project) and switching into zsh before running mkcert -install worked for me.

@ctrl-alter-ego commented on GitHub (Apr 12, 2024): I also had this problem (yes, with this project) and switching into `zsh` before running `mkcert -install` worked for me.

kerem referenced this issue

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

[PR #359] [CLOSED] release arm64 binaries #453