3 ms·
This sounds like a certificate problem, or the browser trying to use https on an HTTP port. If you've deployed Let's Encrypt on the same host, the browser might
by jeroenhd 6y ago
This sounds like a certificate problem, or the browser trying to use https on an HTTP port. If you've deployed Let's Encrypt on the same host, the browser might force the connection to work over HTTPS because Let's Encrypt often adds a so-called HSTS header to the config.
If it's just Chrome not trusting the certificate, you can usually override the error by clicking "details" and then continuing by clicking a link. If the override isn't there (because of HSTS or similar), you can type "thisisunsafe" into the web page to override any non-technical certificate errors (there's no input field but it'll work)