From 6c2982563145e00afcba6c7eeedc2b600232e48f Mon Sep 17 00:00:00 2001 From: Ward Vandewege Date: Tue, 1 Mar 2022 12:44:25 -0500 Subject: [PATCH] 18785: documentation: mention the possible need for chained certificates in the bring-your-own certificates case. Arvados-DCO-1.1-Signed-off-by: Ward Vandewege --- doc/_includes/_install_custom_certificates.liquid | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/_includes/_install_custom_certificates.liquid b/doc/_includes/_install_custom_certificates.liquid index 80878c0498..da6725976f 100644 --- a/doc/_includes/_install_custom_certificates.liquid +++ b/doc/_includes/_install_custom_certificates.liquid @@ -35,4 +35,6 @@ ${CUSTOM_CERTS_DIR}/keepproxy.key +All certificate files will be used by nginx. You may need to include intermediate certificates in your certificate files. See "the nginx documentation":http://nginx.org/en/docs/http/configuring_https_servers.html#chains for more details. + Make sure that all the FQDNs that you will use for the public-facing applications (API/controller, Workbench, Keepproxy/Keepweb) are reachable. -- 2.39.5