From 4729220edaf326744cbbdf92ba93da5f92506b2a Mon Sep 17 00:00:00 2001 From: pini-gh Date: Mon, 27 May 2024 20:43:09 +0200 Subject: [PATCH] fix: bad wording about missing certificate Co-authored-by: Nicolas Duchon --- docs/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/README.md b/docs/README.md index 829a6b3..eb7e7e2 100644 --- a/docs/README.md +++ b/docs/README.md @@ -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: