Open jerico opened 1 year ago
+1
The above workaround steps didn't quite work for me, but I may not have followed them exactly, what did work for me:
mkcert -CAROOT
in PowerShell to get where root certificate is installed in Windows hostcomposer server ssl exec -- -CAROOT
to get where the generated root certificate is storedrun mkcert -install
- this will install the generated root certificate from Windowscomposer server ssl exec -- -uninstall; composer server ssl exec -- -install
to update to root cert from windowscomposer server ssl generate {project domain name}
to generate new domain cert for project using windows root CAAdditionally to get firefox browser to accept the cert, additional step is required -- only impacts FF
Go to: about:preferences#privacy -> View Certificates -> Authorities -> Import
Select rootCA.pem
from installed directory in step 2 from above
Thanks for the extra testing! Interesting though, mkcert is meant to install directly into Firefox's CA root store as well so might be something a bit dodgy there; were there any messages about that when you ran mkcert -install
?
Yep, seems to be specific to windows
mkcert -install The local CA is already installed in the system trust store! 👍 Note: Firefox support is not available on your platform. ℹ️
Aha, thanks!
Steps to reproduce:
mkcert
has generated is only getting installed inside WSL2Workaround:
mkcert
in Windows host a. Install Chocolatey https://chocolatey.org/install b. Runchoco install mkcert
in PowerShellmkcert -CAROOT
in PowerShell to get where root certificate is installed in Windows hostcomposer server ssl exec -- -CAROOT
to get where the generated root certificate is stored\\wsl$\
and browse to the WSL’s CA root directory (e.g.\\wsl$\Ubuntu-20.04\home\jerico\.local\share\mkcert
)rootCA.pem
androotCA-key.pem
to Windows host CA root directory (Step 2)mkcert -install
- this will install the generated root certificate from WSL2Acceptance criteria: