You can use a separate reverse proxy server if you’d like.ġ. Alternatively, you do not have to use Nginx Proxy Manager, or a reverse proxy server hosted on your Raspberry Pi. If you’d like to use Nginx Proxy Manager, you can learn how to set it up here. In this tutorial, I will be using Nginx Proxy Manager which will be hosted on the same Raspberry Pi. The recommended approach for exposing Bitwarden outside of your local network is by using a reverse proxy. 1.1 Reverse Proxy Setup – Self Host Bitwarden on a Raspberry Pi This is to confirm that everything is loading as expected on the bitwarden server. Connect to the IP address of your Raspberry Pi and Port 8080 to access the web interface. Give the container a few minutes, and it should be healthy.ĩ. Change the Restart Policy to Always, then Deploy the container.Ĩ. Select Volumes, then map the /data container path to the Bitwarden volume we created earlier.ħ.

Finally, publish a new network port and map the host port 8080 to the container port 80.Ħ. Give the container a Name, then in the Image section, add vaultwarden/server:latest so docker pulls the latest image. For this reason, you will have to use that image name (as opposed to what the screenshot is showing).ĥ. This is where all of your important information will be stored, so back up this folder if you’d like to ensure your data is backed up.ĥ/3/21 Update: The bitwardenrs image has been deprecated and renamed to vaultwarden. Technically, you don’t have to install Portainer, but I find it easier to manage my Docker containers that way, so I’ll be using that to install Bitwarden on a Raspberry Pi.ģ. Ensure that you have Docker and Portainer installed on your Raspberry Pi. Conclusion – Self Host Bitwarden on a Raspberry Piġ. 1.3 Enabling Admin Page – Self Host Bitwarden on a Raspberry Pi.1.1 Reverse Proxy Setup – Self Host Bitwarden on a Raspberry Pi.

Synology vaultwarden