starred/mkcert

Fork 0

mirror of https://github.com/FiloSottile/mkcert.git synced 2026-04-25 05:26:03 +03:00

[GH-ISSUE #96] Error running mkcert-v1.2.0-windows-amd64.exe -install #52

New issue

Closed

opened 2026-02-25 22:32:29 +03:00 by kerem · 9 comments

kerem commented

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

Owner

Originally created by @DrDrrae on GitHub (Jan 7, 2019).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/96

I'm receiving an error when runing mkcert 1.2.0 on Windows. I downloaded the prebuilt binary.

Windows 10 1809 17763.195
Running cmd.exe as Administrator.

ERROR: failed to generate CA certificate: asn1: string not valid UTF-8

Originally created by @DrDrrae on GitHub (Jan 7, 2019). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/96 I'm receiving an error when runing mkcert 1.2.0 on Windows. I downloaded the prebuilt binary. Windows 10 1809 17763.195 Running cmd.exe as Administrator. ERROR: failed to generate CA certificate: asn1: string not valid UTF-8

kerem

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

closed this issue
added the
bug

help wanted
labels

kerem commented

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

Author

Owner

@NicolasCARPi commented on GitHub (Jan 7, 2019):

What if you try from Powershell.exe instead of cmd.exe?

@NicolasCARPi commented on GitHub (Jan 7, 2019): What if you try from Powershell.exe instead of cmd.exe?

kerem commented

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

Author

Owner

@adamdecaf commented on GitHub (Jan 7, 2019):

What's the username you're using (on the Windows computer) to run mkcert with? That's put into the certificate.

@adamdecaf commented on GitHub (Jan 7, 2019): What's the username you're using (on the Windows computer) to run mkcert with? That's put into the certificate.

kerem commented

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

Author

Owner

@DrDrrae commented on GitHub (Jan 7, 2019):

Powershell.exe is the same.

Does the computer get used at any point in the process? I just remembered that my computer name is "¡" (upside down exclamation point). I'll try on another computer.

@DrDrrae commented on GitHub (Jan 7, 2019): Powershell.exe is the same. Does the computer get used at any point in the process? I just remembered that my computer name is "¡" (upside down exclamation point). I'll try on another computer.

kerem commented

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

Author

Owner

@adamdecaf commented on GitHub (Jan 7, 2019):

Yep. The hostname as well:

github.com/FiloSottile/mkcert@da4da8a4bc/cert.go (L34-L39)

@adamdecaf commented on GitHub (Jan 7, 2019): Yep. The hostname as well: https://github.com/FiloSottile/mkcert/blob/da4da8a4bc86e0dff9c338c547bb1298220d5433/cert.go#L34-L39

kerem commented

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

Author

Owner

@DrDrrae commented on GitHub (Jan 7, 2019):

That's probably the issue. Doesn't like the upside down exclamation point as the hostname.

@DrDrrae commented on GitHub (Jan 7, 2019): That's probably the issue. Doesn't like the upside down exclamation point as the hostname.

kerem commented

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

Author

Owner

@NicolasCARPi commented on GitHub (Jan 7, 2019):

Using non ascii characters as a hostname sounds like a bad idea from the start, but that's just my 2 cents :) (it reminds me of Mac users putting '/' in filenames and not seeing an issue with that)

@NicolasCARPi commented on GitHub (Jan 7, 2019): Using non ascii characters as a hostname sounds like a bad idea from the start, but that's just my 2 cents :) (it reminds me of Mac users putting '/' in filenames and not seeing an issue with that)

kerem commented

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

Author

Owner

@DrDrrae commented on GitHub (Jan 7, 2019):

My computer name was 🍕 for a while but it caused issues with Windows Subsystem for Linux. Guess I found another issue.

It is, as far as I know, supported in Windows 10 and even works in a domain environment.

@DrDrrae commented on GitHub (Jan 7, 2019): My computer name was 🍕 for a while but it caused issues with Windows Subsystem for Linux. Guess I found another issue. It is, as far as I know, supported in Windows 10 and even works in a domain environment.

kerem commented

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

Author

Owner

@FiloSottile commented on GitHub (Jan 8, 2019):

Unicode should work in certificates, so the issue here seems to be that the hostname output is not UTF-8. Anyone better versed than me on Windows character encodings want to take a look?

@FiloSottile commented on GitHub (Jan 8, 2019): Unicode should work in certificates, so the issue here seems to be that the `hostname` output is not UTF-8. Anyone better versed than me on Windows character encodings want to take a look?

kerem commented

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

Author

Owner

@LuomingXu commented on GitHub (Mar 24, 2019):

same problem...
Windows, v1.3.0

@LuomingXu commented on GitHub (Mar 24, 2019): same problem... Windows, v1.3.0

kerem referenced this issue

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

[PR #59] [CLOSED] Fix use of multiple CAs on Linux #375