• Hello Guest! SynoForum.com is celebrating its 5th anniversary! 🥳🎉 Read more...
BitWarden - self hosted password manager using vaultwarden/server image

Docker BitWarden - self hosted password manager using vaultwarden/server image

Currently reading
Docker BitWarden - self hosted password manager using vaultwarden/server image

7,573
2,276
www.blackvoid.club
NAS
DS718+, DS918+, 2x RS3614RPxs+
Router
  1. RT1900ac
  2. RT2600ac
  3. MR2200ac
Operating system
  1. macOS
Mobile operating system
  1. iOS
Rusty submitted a new resource:

BitWarden - self hosted password manager using mprasil/bitwarden image - Quick tutorial on how to run this in docker

Considering that there are several people interested in this solution, maybe a quick tutorial on how to run this in docker will help.

Let's start.

1st thing - install Docker via Package center or if your NAS doesnt support it, install it manually by downloading the package from Syno site. After that you can use the Manual install button in Pacakge Center to install Docker. Keep in mind that this is not 100% supported and some features of docker will still not function. If your nas is from...

Read more about this resource...
 
Why not leave port 3012 mapped to "auto"?
Sure you can leave it on auto. Personally, I don't like to do that and have all those dynamic ports set as static. When you have several containers running sure but when you have 30,40+ it gets hectic. This port is for WebSockets notifications, yes.
 
Now that you have your new BW selfhosted instance running, enjoy it and prepare to make it accessible via the internet using a valid SSL certificate, a custom domain name and revers proxy. More on that in the upcoming tutorial.
Hope all that can be done via Let's encrypt on my NAS for certificate and synology domain that I use for my DDNS ;)
 
Hope all that can be done via Let's encrypt on my NAS for certificate and synology domain that I use for my DDNS
Well, ofc it can. If you already have a LE cert and ddns domain on your NAS active, then just use the Control Panel > Application Portal > Revers proxy to configure record that will point a custom name to your docker BW installation.

Do you have a preferred url in mind?
 
Do you have a preferred url in mind?
I already have Synology DDNS URL. Do I have to create a new one for Bitwarden?


You've lost me here:

37



:coffee:
 
I already have Synology DDNS URL. Do I have to create a new one for Bitwarden?


You've lost me here:

View attachment 37


:coffee:
So, Source needs to be your end result url and port, and a destination is your local docker container destination.

In your case, the source will be https, url, and port (guessing 443 if you don't wanna use a custom number in the url). On the destination side it will be http, ip address of your nas and port that bw is using (the port that you have used against bw port 80).

For example, it should look like this:

38
 
1st off if your are using any port (even 443) you will have to sort port forwarding, ofc. 2nd if your certificate doesn't cover any other subdomain names, then yes you will have to have a different cert.

One option would be a wild card certificate the other would be a regular cert that has multiple SAN (subject alternate names) values in it.
 
1st off if your are using any port (even 443) you will have to sort port forwarding
So I'll need to add [myportnumber] to my router port forwarding?


2nd if your certificate doesn't cover any other subdomain names, then yes you will have to have a different cert.
It covers that [name].synology.me I already have, so I guess that's ok.
 
The port that you will use when accessing BW from the internet needs to be forwarded to your NAS IP. On top of this, you need to configure reverse record that will use that forwarded port (added in source section) to your docker container port for bw web ui (in the destination section).
 
The port that you will use when accessing BW from the internet needs to be forwarded to your NAS IP.
I add this to my router port forwarding:
41



On top of this, you need to configure reverse record that will use that forwarded port (added in source section) to your docker container port for bw web ui (in the destination section).
Lost me again... Sorry, I'm still new to all this networking stuff. :(
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

So this means that I can copy to its directory from another DiskStation directory and share (using File...
Replies
3
Views
1,488
I'll delete everything I can containers/images/etc, and start fresh over the weekend. While I really like...
Replies
48
Views
6,763
I use it with the Reeder app and wanted to have filtered feeds there. I'll play around with it a bit more.
Replies
61
Views
10,091
I ran across a very complete how-to-install-nextcloud on Docker using the Synology UI (just the UI, not...
Replies
28
Views
8,365
Hello, i just tried to follow these steps above, but all I get is a psql: could not connect to server...
Replies
43
Views
11,512
I discovered if you use fireflyiii/core:latest everything works just fine
Replies
35
Views
16,941

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Back
Top