From df8d2c62c07d4b153707e8c1cd99518383c0c6c0 Mon Sep 17 00:00:00 2001 From: muibusan Date: Thu, 15 Aug 2019 13:52:27 +0200 Subject: [PATCH] Added ROCKET_TLS line example --- Enabling-HTTPS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Enabling-HTTPS.md b/Enabling-HTTPS.md index f7ee290..67faa3c 100644 --- a/Enabling-HTTPS.md +++ b/Enabling-HTTPS.md @@ -22,7 +22,7 @@ docker run -d --name bitwarden \ You need to mount ssl files (-v argument) and you need to forward appropriate port (-p argument), usually 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`. -For further information on how to set up and use a private CA on your local system refer to [this chapter of the wiki.](https://github.com/dani-garcia/bitwarden_rs/wiki/Private-CA-and-self-signed-certs-that-work-with-Chrome) +For further information on how to set up and use a private CA on your local system refer to [this chapter of the wiki.](https://github.com/dani-garcia/bitwarden_rs/wiki/Private-CA-and-self-signed-certs-that-work-with-Chrome) After following it your ROCKET_TLS line could look like this: `-e ROCKET_TLS='{certs="/ssl/bitwarden.crt",key="/ssl/bitwarden.key"}' \` Due to what is likely a certificate validation bug in Android, you need to make sure that your certificate includes the full chain of trust. In the case of certbot, this means using `fullchain.pem` instead of `cert.pem`.