running the bitwarden_rs server without https) the it works just fine. When I remove the enviroment variable ROCKET_TLS (i.e. I've been at this for a while and still no luck. I've double and triple checked the location of my ssl certificates and that they match up. Which is the same error I get when I incorrectly name the ssl certificates upon running it with Docker. This provides TLS termination for both the web-based vault interface and. I'm trying to run it using docker compose and keep getting the error below. A reverse proxy ( Nginx Proxy Manager) is configured in front of the Docker container. If you encounter any bugs, please report them, Daniel is usually fixing them in a matter of hours.ĭisclaimer: I'm one of the bitwarden_rs contributors, apologies if this kind of self-promotion is not allowed here.Currently I'm successfully running bitwarden_rs on Docker. I've been using it for a while without any issues so far. Please give it a go and report any bugs encountered. I've made a bitwarden docker image (you can see the source code here) so if you use docker, the deployment is as simple as one docker run command. This gives you the full Bitwarden experience with no artificial limits or license required including password sharing. I'm not sure however my setup is bullet proof.

I've created a second docker postgresql instance and managed to setup a 'Warm backup' where the WOL is transferred to second machine. Serving the static files for Vault (web) interface With this setup it's possible to run HA bitwardenrs, however it's the data within the database you need to protect - not necessarily the bitwardenrs instance. While being small, it still supports all (relevant) API functionality, like: It's very resource efficient implementation (uses about 10MB of RAM, close to no CPU) written by Daniel García. Let me introduce you to bitwarden_rs, which is Bitwarden API implementation written in Rust.

Bitwarden_rs docker