fix: bad wording about missing certificate

Co-authored-by: Nicolas Duchon <nicolas.duchon@gmail.com>
This commit is contained in:
pini-gh 2024-05-27 20:43:09 +02:00 committed by GitHub
parent 3ef2afb687
commit 4729220eda
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -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: