**
**If it is nginx, when the domain name accessed does not match the certificate, chrome will continue to access.
However, if it is caddyserver, it returns a connection refuse.
How to close this verification certificate?
**
**If it is nginx, when the domain name accessed does not match the certificate, chrome will continue to access.
However, if it is caddyserver, it returns a connection refuse.
How to close this verification certificate?
I doubt this is true, or at least the whole story.
The only way to make the client accept the certificate (assuming a robust implementation of TLS verification, like Chrome has) is to provide a certificate that matches the host being requested in the URL.
You’ll have to configure Caddy to serve a certificate that matches the IP address in your URL bar.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.