mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 13:36:02 +03:00
[GH-ISSUE #51] Installing in Firefox failed... The local CA is now installed in the Firefox trust store... #30
Labels
No labels
TLS stack issue
Windows
bug
duplicate
duplicate
enhancement
help wanted
help wanted
pull-request
question
question
root store
waiting for info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mkcert#30
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @leepeterson on GitHub (Aug 9, 2018).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/51
I use Firefox Developer Edition. I also install apps in
$HOME/Applications. I've symlinked$HOME/Applications/Firefox Developer Edition.appto/Applications/Firefox.appin an effort to possibly solve this mkcert issue. Perhaps I've solved it given the output I see:But I'm a bit confused about what's actually happened. "Using local CA... Firefox installation failed... local CA is now installed in Firefox..."
That said, I have made good use of mkcert: system keychain trusts the root, certs are created for local vhosts, paths to ipv4 & ipv6 pem files are correctly set in Nginx conf files, browsers are validating the certs... but perhaps I'm taking the long way around it.
Any clarification would be greatly appreciated.
@FiloSottile commented on GitHub (Aug 13, 2018):
@leepeterson I should have fixed both the missed detection of Firefox Developer Edition, and the misleading message, but I'm not sure if that will fix the root issue.
Can you try the latest master, and if it doesn't work report the output of
ls $HOME/Library/Application Support/Firefox/Profiles/?@FiloSottile commented on GitHub (Jan 7, 2019):
Timeout in waiting for info state. Please reopen if the root issue is still present.