-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After mkcert I get "Potential Security Risk" warning #164
Comments
You might need to configure node.js to look at the mkcert CA location. Maybe #78 (comment) ? |
I very rarely reboot my system, however, a couple of days ago I did due to a kernel update and then when I started once again tinkering with mkcert it stated working just fine... go figure. :) |
Probably it took a browser restart, glad it works now! |
Not working for me after browser restart, in below browsers!!!
What I didbrew install mkcert
brew install nss
mkcert --install
mkcert localhost 127.0.0.1 After this steps, restarted browsers OS = macOS Bigsur |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I installed mkcert in ArchLinux.
Installation was smooth. No issues, no warnings.
I run
Everything was fine and I was "told" by the installer that Firefox and Chrome/Chromium had been included.
I then run in my dev environment:
The server started on https://localhost:8040 but ... when I go to the page I get warnings of not being secure.
Also while testing a mailchip api the browser rejects the connection due to CORS given that my connection is not secure.
Could you help me fix these problems.
Thanks!!
The text was updated successfully, but these errors were encountered: