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

Secured domains's certificate not trusted. #79

Closed
pavinthan opened this issue Jul 6, 2017 · 6 comments
Closed

Secured domains's certificate not trusted. #79

pavinthan opened this issue Jul 6, 2017 · 6 comments

Comments

@pavinthan
Copy link

pavinthan commented Jul 6, 2017

NET::ERR_CERT_AUTHORITY_INVALID
trustCertificate method, may you please fix.

OS - Ubuntu 17.04 64-bit
Browser - Version 59.0.3071.115 (Official Build) (64-bit)

@pavinthan pavinthan changed the title Secured domains: Secured domains's certificate not trusted . Jul 6, 2017
@pavinthan pavinthan changed the title Secured domains's certificate not trusted . Secured domains's certificate not trusted. Jul 6, 2017
@TheNodi
Copy link
Collaborator

TheNodi commented Jul 7, 2017

Valet generates a Self-signed Certificate when "securing" a domain. This allows you to test out HTTPS on your local machine during development, valet is NOT a production tool to serve your website to the public.

You are seeing this error because the certificate has not been issued by an authorized certificate authority. On Chrome press "Advanced" and "Proceed to ...." to bypass the error screen.

You can learn more about HTTPS and how certificates work here:

@TheNodi TheNodi closed this as completed Jul 7, 2017
@pavinthan
Copy link
Author

pavinthan commented Jul 7, 2017

I understood but Valet create certificate authorities in ubuntu 16.04 if the certificate have authority it will trust by machine otherwise it will failed the issue is the same process did not created the authority for the certificate, currently chrome not allowed invalid certificate for use services such as geolocation and service worker, payment api, if you need this kind of certificate you don't need to create for every domain you can use localhost certificate for the https word. Please care it.

@TheNodi
Copy link
Collaborator

TheNodi commented Jul 7, 2017

I apologies for that, I completely forgot we were trying to trust the self-signed certificate.

The command is still valid looking at the chromium wiki, so it's pretty strange it isn't working.

Have you closed and reopened chrome after securing the site? Is libnss3-tools installed? Does it work on firefox?

You can verify if the certificate has been inserted in the database using:

certutil -d sql:$HOME/.pki/nssdb -L

And you can try to insert it manually (to see if there're errors) using:

certutil -d sql:$HOME/.pki/nssdb -A -t TC -n "site_name.dev" -i "/home/your_user/.valet/Certificates/site_name.dev.crt"

@TheNodi TheNodi reopened this Jul 7, 2017
@cpriego
Copy link
Owner

cpriego commented Jul 9, 2017

Fixed in release v2.0.20

@cpriego cpriego closed this as completed Jul 9, 2017
@stephan-v
Copy link

This is not fixed, the certificate is properly added in chrome but I am still getting:

NET::ERR_CERT_AUTHORITY_INVALID

@chiptu
Copy link

chiptu commented Aug 20, 2020

I had the same problem just go into your browser -> certifcate -> authorities -> import LaravelValetCASelfSigned

LaravelValetCASelfSigned is place in your $HOME/.valet/CA

Then if you re on chrome just enable this parameter chrome://flags/#allow-insecure-localhost .

If you re not on chrome you should have a parameter like this to find.

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

5 participants