You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Used mkcert for years, macOS, iOS, iPadOS, Linux. Local and cross-machine use (copying rootCA). No problems, outside the usual PEBKAC. Thanks much for that!
One thing I have never gotten to work, despite years of trying on a variety of machines, is a rootCA created on macOS and copied to Windows. mkcert on Windows always reports success. -install modal clearly shows all expected info about the rootCA coming from mac. -uninstall prompt data matches expected as well. Apparently all is well. But both Edge and Chrome report invalid CA's. FF is unsupported I believe so I've not ever checked that. The certs presented by both browsers warning GUIs appear exactly as expected. Hitting the same server from the same machine as is running the server process and from different macOS machine and from iOS/iPadOS machines also works without issue (once the rootCA is correctly copied over).
Steps take:
Generate keys for macOS server and verify using a local browser then an external iOS device.
Copy rootCA.pem from macOS's mkcert -ROOTCA
Paste to Windows dir reported by Windows' mkcert -ROOTCA
mkcert -uninstall on Windows, mkcert -install on Windows.
Verify install popup info matches what I made on macOS.
Reboot Windows (come on, it's Windows).
Nav to macOS server in Edge and in Chrome.
Could there be other steps required to get a rootCA made on mac to install and "work" on Windows 10? Any diagnostic steps to take "see" more about what's going? With only the readme and -help, it all seems a bit of a black box; either works great or gives you the middle finger sans detail.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Used mkcert for years, macOS, iOS, iPadOS, Linux. Local and cross-machine use (copying rootCA). No problems, outside the usual PEBKAC. Thanks much for that!
One thing I have never gotten to work, despite years of trying on a variety of machines, is a rootCA created on macOS and copied to Windows. mkcert on Windows always reports success. -install modal clearly shows all expected info about the rootCA coming from mac. -uninstall prompt data matches expected as well. Apparently all is well. But both Edge and Chrome report invalid CA's. FF is unsupported I believe so I've not ever checked that. The certs presented by both browsers warning GUIs appear exactly as expected. Hitting the same server from the same machine as is running the server process and from different macOS machine and from iOS/iPadOS machines also works without issue (once the rootCA is correctly copied over).
Steps take:
mkcert -ROOTCA
mkcert -ROOTCA
Could there be other steps required to get a rootCA made on mac to install and "work" on Windows 10? Any diagnostic steps to take "see" more about what's going? With only the readme and -help, it all seems a bit of a black box; either works great or gives you the middle finger sans detail.
Beta Was this translation helpful? Give feedback.
All reactions