From 1a5889197bc55c55f572e0895a9828d697cd998b Mon Sep 17 00:00:00 2001 From: Jeremy Lin Date: Sat, 27 Feb 2021 13:44:14 -0800 Subject: [PATCH] Updated Enabling HTTPS (markdown) --- Enabling-HTTPS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Enabling-HTTPS.md b/Enabling-HTTPS.md index da7aa16..72ba202 100644 --- a/Enabling-HTTPS.md +++ b/Enabling-HTTPS.md @@ -53,7 +53,7 @@ docker run -d --name bitwarden \ You need to mount ssl files (-v argument) and you need to forward appropriate port (-p argument), usually port 443 for HTTPS connections. If you choose a different port number than 443 like for example 3456, remember to explicitly provide that port number when you connect to the service, example: `https://bitwarden.local:3456`. -:warning: Especially if you're having problems with this on Android, make sure that your certificate file includes the full chain of trust. In the case of certbot, this means using `fullchain.pem` instead of `cert.pem`. The full chain should include two certs: the leaf cert (same as what's in `cert.pem`), followed by an R3 or E1 [intermediate cert](https://letsencrypt.org/certificates/#intermediate-certificates). Many Android vendors don't do a great job providing proper OS updates, and may not include up-to-date Let's Encrypt intermediate certs in their system trust store. +:warning: Make sure that your certificate file includes the full chain of trust. In the case of certbot, this means using `fullchain.pem` instead of `cert.pem`. The full chain should include two certs: the leaf cert (same as what's in `cert.pem`), followed by an R3 or E1 [intermediate cert](https://letsencrypt.org/certificates/#intermediate-certificates). For example, Android by default does not include any Let's Encrypt intermediate certs in their system trust store, so the Android client will likely fail to connect if you don't provide the full chain. Software used for getting certs often use symlinks. If that is the case, both locations need to be accessible to the docker container.