|
@@ -579,8 +579,9 @@ _WARNING_: HSTS will force your users to visit the HTTPS version of your site fo
|
|
|
### Missing Certificate
|
|
### Missing Certificate
|
|
|
|
|
|
|
|
If no matching certificate is found for a given virtual host, nginx-proxy will:
|
|
If no matching certificate is found for a given virtual host, nginx-proxy will:
|
|
|
-* configure nginx to use the default certificate (`default.crt` with `default.key`) and return a 500 error for HTTPS,
|
|
|
|
|
-* force enable HTTP; i.e. `HTTPS_METHOD` will switch to `noredirect` if it was set to `nohttp` or `redirect`.
|
|
|
|
|
|
|
+
|
|
|
|
|
+- configure nginx to use the default certificate (`default.crt` with `default.key`) and return a 500 error for HTTPS,
|
|
|
|
|
+- force enable HTTP; i.e. `HTTPS_METHOD` will switch to `noredirect` if it was set to `nohttp` or `redirect`.
|
|
|
|
|
|
|
|
If the default certificate is also missing, nginx-proxy will configure nginx to accept HTTPS connections but fail the TLS negotiation. Client browsers will render a TLS error page. As of March 2023, web browsers display the following error messages:
|
|
If the default certificate is also missing, nginx-proxy will configure nginx to accept HTTPS connections but fail the TLS negotiation. Client browsers will render a TLS error page. As of March 2023, web browsers display the following error messages:
|
|
|
|
|
|
Nicolas Duchon