fix: bad wording about missing certificate
Co-authored-by: Nicolas Duchon <nicolas.duchon@gmail.com>
This commit is contained in:
parent
3ef2afb687
commit
4729220eda
1 changed files with 2 additions and 2 deletions
|
@ -572,8 +572,8 @@ _WARNING_: HSTS will force your users to visit the HTTPS version of your site fo
|
|||
|
||||
### Missing Certificate
|
||||
|
||||
If HTTPS is enabled for a virtual host but its certificate is missing, nginx-proxy will:
|
||||
* configure nginx to use the default certificate (`default.crt` with `default.key`) and return a 500 error,
|
||||
If no matching certificate is found for a given virtual, 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`.
|
||||
|
||||
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:
|
||||
|
|
Loading…
Reference in a new issue