If, by chance, you have never looked at the truly excellent Vaultwarden wiki then this is my attempt to publicise the effort that clever people have put in to explain and document their work. Job done, without any attempt to further secure it. In the Real World away from forums and the like, I have exactly two friends who have installed Vaultwarden on their NAS and they each found a basic tuto in their native tongue and followed it. I have the view that (a) my password manager is THE most important content in my digital life, and (b) I am by no means an expert in software or digital security, so therefore I have to do what I can to protect My Secret Stuff from nefarious persons. Finally a direct contribution to This Place, I would like to give some hints on making your Vaultwarden install a little more secure. If you would like directions in visual format then check out my YouTube video that runs through the setup.Greetings. Docker-compose Caddy with DNS challenge.Running a private vaultwarden instance with Let’s Encrypt certs.I referenced the following links for much of the setup description below. See step 12 in the Setup Steps below to set the custom ports. The url to access Vaultwarden would look something like. The setup will be using the Caddy web server that will obtain a Let's Encrypt certificate for a subdomain that is setup through Duck DNS.īecause Synology NASs use both ports 80 and 443 for DSM we'll need to use a custom port number when accessing Vaultwarden.

This repository will provide you the details to run a private, LAN access only, instance of Vaultwarden, using docker-compose, on a Synology NAS.

Run A Private, LAN Access Only, Instance Of Vaultwarden On A Synology NAS With Docker-Compose Description

Synology vaultwarden