Test the accesses and start the Birwarden_RS fine tune at. If everything goes well, the prompt will let you know the containers are started and wait until a ctrl + C is triggered to stop them. Ready for a first run : docker-compose -f docker-compose_bitwarden-caddy.yml up.Pull needed images docker-compose -f docker-compose_bitwarden-caddy.yml pull.Gain root using sudo -i with your admin password.Connect your admin account with password.
Make sure webstation is running with a dummy page to be served.In Custom Headers tab, click the drop down list next to add button and choose websockets.Go to Settings > Application Portal > Reverse proxy.
You'll need to disable the admin panel from itself. Beware, if accessed once, it will be enabled in /data/config.json whatever are the Environment variables. You will first need to access the admin page to fine tune the Vaultwarden server. Copy this repo content to /volumeX/docker/.Unzip and review docker-compose_bitwarden-caddy.yml settings.Folder used : /volumeX/docker/ to be personnalized to your DSM setup.This part is off-topic here.Īs convention, we will use as example the following A domain name with Let's Encrypt certs enabled.This is the reason why Vaultwarden server is not set to use SSL because behind 2 proxies.ĭespite this has been made to run on Synology NAS, this should run on other systems with / without minor adaptations. We will use the embedded reverse proxy and forward the request on some other ports. Synology do not allow advanced setting of their Nginx reverse proxy and ports 80/443 are not free. This is the reason why caddy server is used to enable the websocket notifications. The goal is to keep the Synology NAS system untouched to be upgrade-proof. This setup provides a Vaultwarden server with support of websocket notifications. Thanks a lot for being such a great community!ĮDIT: As pointed out in the comments, this is for bitwarden_rs which is written in Rust.Docker Vaultwarden proxified for Synology NASĪ docker-compose ready package to run Vaultwarden proxified with Caddy server. Not sure if this will help anyone else, but I figured I would share the process I used to setup/configure this on my NAS: I'm really looking forward to emergency access being added later this year/early next year, as this was the only feature I felt like I really needed that I didn't have!Īnyways, self-hosting was always something I was interested in but a little intimidated by. Major props to the devs for creating an amazing, transparent password manager. Out of all the applications I've used, bitwarden has become my favorite and I have slowly converted everyone close to me into a bitwarden user.
I've been using bitwarden for the past 4-5 years (switched from LastPass) and couldn't be happier. I created a video/tutorial on how to self-host bitwarden on a Synology NAS and wanted to share.
0 kommentar(er)
