[GH-ISSUE #559] Segmentation fault when attempting mkcert -install (mkcert installed by brew), mkcert intalled via apt-get works - 1.4.3, 1.4.4 #330

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

Originally created by @therobyouknow on GitHub (Nov 24, 2023).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/559

Environment

  • Operating system (including version):
    Ubuntu 22.04 running in WSL2 on Windows 10 64 Bit Pro, 32GB RAM machine
  • mkcert version (from mkcert -version):
    none reported:
$ mkcert -version
Segmentation fault
  • Server (where the certificate is loaded):
    don't know sorry

  • Client (e.g. browser, CLI tool, or script):
    terminal

What you did

Ran Ubuntu in WSL2, got terminal, then:

$ mkcert -install
Segmentation fault

What went wrong

Segmentation fault
Originally created by @therobyouknow on GitHub (Nov 24, 2023). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/559 ## Environment * Operating system (including version): Ubuntu 22.04 running in WSL2 on Windows 10 64 Bit Pro, 32GB RAM machine * mkcert version (from `mkcert -version`): none reported: ``` $ mkcert -version Segmentation fault ``` * Server (where the certificate is loaded): don't know sorry * Client (e.g. browser, CLI tool, or script): terminal ## What you did Ran Ubuntu in WSL2, got terminal, then: ``` $ mkcert -install Segmentation fault ``` ## What went wrong ``` Segmentation fault ```
Author
Owner

@therobyouknow commented on GitHub (Nov 25, 2023):

I tried deleting the Ubuntu distro and recreating it, and then attempting to re-install mkcert via brew. Same error. 100% repeatable.

I then tried installing mkcert via apt-get and it worked - no longer the segmentation fault. version of mkcert v1.4.3 installed via that method. However, subsequent activity involving apt-get updated it to 1.4.4 and it still worked.

On that basis, my conclusion so far seems to be a problem with how brew installs mkcert.

<!-- gh-comment-id:1826435336 --> @therobyouknow commented on GitHub (Nov 25, 2023): I tried deleting the Ubuntu distro and recreating it, and then attempting to re-install mkcert via brew. Same error. 100% repeatable. I then tried installing mkcert via apt-get and it worked - no longer the segmentation fault. version of mkcert v1.4.3 installed via that method. However, subsequent activity involving apt-get updated it to 1.4.4 and it still worked. On that basis, my conclusion so far seems to be a problem with how brew installs mkcert.
Author
Owner

@hrivano commented on GitHub (Jan 31, 2024):

same problem here with an ubuntu distro (not inside wsl)

<!-- gh-comment-id:1919365140 --> @hrivano commented on GitHub (Jan 31, 2024): same problem here with an ubuntu distro (not inside wsl)
Author
Owner

@eleflea commented on GitHub (Aug 4, 2025):

same problem

<!-- gh-comment-id:3151408652 --> @eleflea commented on GitHub (Aug 4, 2025): same problem
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/mkcert#330
No description provided.