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. Vaultwarden is the name of the docker image that allows Bitwarden to work locally on your Synology NAS.Docker Vaultwarden proxified for Synology NASĪ docker-compose ready package to run Vaultwarden proxified with Caddy server. Note: Bitwarden will always be called Bitwarden and not Vaultwarden.
There are no major changes in the process, it’s just the name of the image that was changed from bitwardenrs/server to vaultwarden/server. Connect that new container to your current /data volume. Everything will be just as before. Create a new container with the same identical settings, but using the new image: vaultwarden/server. Stop your current bitwardenrs/server container then delete it. If you have the old image, bitwardenrs/server, just download the new image: vaultwarden/server. In the meantime I have also updated my Bitwarden articles How to install Bitwarden on Your Synology NAS and How to Allow BitWarden to Work Over an HTTPS Connection So the upgrade is as simple as removing the old container and creating a new one with the new image, making sure the rest of the parameters are the same. The new image for bitwarden is now vaultwarden/server which is equivalent to the old one, except for the name. Starting yesterday, the bitwardenrs/server and bitwardenrs/server-mysql images have become deprecated in the Docker Registry.
0 kommentar(er)
