Closed abr4xas closed 2 years ago
You just need to click "Advanced" then "Continue to localhost (unsafe)" to access your application. *The warning from the browser is normal behavior because the server uses a self-signed certificate.
@ryoluo the issue is not about that the browser detects that the certificate is self-signed, the problem is that once you click "Advanced", the problem with Chrome (or Chrome based browsers like Brave) is that the message is the following:
"
You cannot visit
You see the "because the website sent scrambled credentials that Chrome cannot process" that's the real issue.
@aguvillalba I got it. Actually this is not a library's issue, but you can ignore the caution by typing "thisisunsafe" on the page. Ref: https://snippets.khromov.se/bypass-chrome-self-signed-certificate-not-working-error-page/
When you get to this screen, you may type thisisunsafe
in the "air", and it'll overpass this.
Meaning, on this page, you don't click anything, just type that and it'll continue.
Isn't the purpose of having SSL is that the local certificate is valid? For example, in Laragon the certificate .crt is added to TrustStore.
Validation of self-signed certificate is out of scope because it is the issue of the SSL client, not the server.
Very convenient plugin. Thank you.
For this question I want to advice this answer by kellen for google chrome https://stackoverflow.com/questions/7580508/getting-chrome-to-accept-self-signed-localhost-certificate
Any advice on how to make it work ?