See the bitwarden_rs wiki for more information on how to configure and run the bitwarden_rs server. Some proxies automatically do this step, like Caddy (see examples linked above).

If you have an available domain name, you can get HTTPS certificates with Let's Encrypt, or you can generate self-signed certificates with utilities like mkcert. This can be configured in bitwarden_rs directly or using a third-party reverse proxy ( some examples). To solve this problem, you need to access the web vault from HTTPS.

In this case, you might get an error like Cannot read property 'importKey'. IMPORTANT: Some web browsers, like Chrome, disallow the use of Web Crypto APIs in insecure contexts. This will preserve any persistent data under /bw-data/, you can adapt the path to whatever suits you. Pull the docker image and mount a volume from the host for persistent storage: docker pull bitwardenrs/server:latestĭocker run -d -name bitwarden -v /bw-data/:/data/ -p 80:80 bitwardenrs/server:latest Serving the static files for Vault interface.DO NOT use the official support channels.īasically full implementation of Bitwarden API is provided including: ⚠️ IMPORTANT⚠️: When using this server, please report any bugs or suggestions to us directly (look at the bottom of this page for ways to get in touch), regardless of whatever clients you are using (mobile, desktop, browser.). This project is not associated with the Bitwarden project nor 8bit Solutions LLC. Image is based on Rust implementation of Bitwarden API. This is a Bitwarden server API implementation written in Rust compatible with upstream Bitwarden clients*, perfect for self-hosted deployment where running the official resource-heavy service might not be ideal.

Keeweb docker