vw_small

commit 08c55f636a85e1c5d51508dc0b6b370087fbd7bb
parent 0dc5d1a1c649fbb71c5e74a032ae40fdad5954b9
Author: Daniel García <dani-garcia@users.noreply.github.com>
Date:   Tue,  8 Jan 2019 21:51:09 +0100

Mention HTTPS needed for Chrome
Diffstat:
M
README.md
 | 
6
++++++

1 file changed, 6 insertions(+), 0 deletions(-)
diff --git a/README.md b/README.md
@@ -37,6 +37,12 @@ docker run -d --name bitwarden -v /bw-data/:/data/ -p 80:80 mprasil/bitwarden:la
 ```
 This will preserve any persistent data under /bw-data/, you can adapt the path to whatever suits you.
 
+**IMPORTANT**: Some web browsers, like Chrome, disallow the use of Web Crypto APIs in insecure contexts. In this case, you might get an error like `Cannot read property 'importKey'`. To solve this problem, you need to access the web vault from HTTPS. 
+
+This can be configured in [bitwarden_rs directly](https://github.com/dani-garcia/bitwarden_rs/wiki/Enabling-HTTPS) or using a third-party reverse proxy ([some examples](https://github.com/dani-garcia/bitwarden_rs/wiki/Proxy-examples)).
+
+If you have an available domain name, you can get HTTPS certificates with [Let's Encrypt](https://letsencrypt.org/), or you can generate self-signed certificates with utilities like [mkcert](https://github.com/FiloSottile/mkcert). Some proxies automatically do this step, like Caddy (see examples linked above).
+
 ## Usage
 See the [bitwarden_rs wiki](https://github.com/dani-garcia/bitwarden_rs/wiki) for more information on how to configure and run the bitwarden_rs server.