The name is arbitrary, mine's bitwardenrs. Go to Images in the Docker interface and launch it. Go to the Registry in the Docker interface (Install Docker from the Package Manager if you haven't already) and download the image for bitwardenrs/server:latest. Which is where your Docker container is going to be. Destination is HTTP, localhost, port 8123. Just give it a good name like "Bitwarden" for source choose HTTPS, hostname is, port 443. (Application Portal -> Reverse Proxy -> Create). This way you can have multiple services be reachable on the https port with different (sub-)domains. I'm going to use 8123 here, but any port is fine. This forwards requests to your new (sub-domain) from port 443 (https) to the port the Docker container is running on. (Settings -> Security -> Certificates -> Add) If you already have one for other services, don't worry you can have multiple certificates for different (sub-)domains. This one's easy through the interface and Let's Encrypt. Mine's hosted at, so I created a CNAME entry for my existing setup. Therefore I decided to install dani-garcia/bitwarden_rs on my Synology NAS in a Docker container. What I don't get though is why I would have to pay a monthly subscription fee for the premium features even if I host it myself. Being an open protocol you can obviously host it yourself.
All normal functionality (imho) is available for free, premium costs 10$/year or for a family of up to five its 12$/year (1$/month). The concept is simple: It's FOSS, everything is encrypted client side. It automatically spawns a second container, backing up the database so I can run a backup of my passwords. UPDATE: Instead of manually setting up the Docker container, I now use docker-compose to set it up. After Setting up my old and trusted KeePass+Nextcloud Combo and struggling with synchronization conflicts as well as integration problems with Firefox, I decided to give Bitwarden a go.
0 kommentar(er)
