Skip to content
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

Closed
ralvez opened this issue May 24, 2019 · 4 comments
Closed

After mkcert I get "Potential Security Risk" warning #164

ralvez opened this issue May 24, 2019 · 4 comments

Comments

@ralvez
Copy link

ralvez commented May 24, 2019

I installed mkcert in ArchLinux.
Installation was smooth. No issues, no warnings.
I run

mkcert -install and mkcert localhost.

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:

npx vue-cli-service serve --https --port 8040

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!!

@adamdecaf
Copy link
Contributor

You might need to configure node.js to look at the mkcert CA location. Maybe #78 (comment) ?

@ralvez
Copy link
Author

ralvez commented May 29, 2019

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. :)
Thanks for your reply.

@FiloSottile
Copy link
Owner

Probably it took a browser restart, glad it works now!

@awkward-minion
Copy link

awkward-minion commented Jul 10, 2022

Not working for me after browser restart, in below browsers!!!

  • Safari
  • Chrome
  • Firefox

What I did

brew 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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants