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

[Evander]

Are you using rp for bw as a custom conf file or what?

I followed your guide to install BitWarden, then installed the reverse proxy for BitWarden to use with my custom domain. Now I’m trying to remove the reverse proxy, and instead install custom_rp.conf from your code.

 

[Rusty]

Ok so not really sure what the problem here is? Do you have an error of some sort or are you just wondering what ports to use?

 

[Evander]

Ok so not really sure what the problem here is? Do you have an error of some sort or are you just wondering what ports to use?

I've been getting errors, and cannot connect to the BitWarden, and I'm presuming it's a port problem, so I'm wondering given the settings that work in my previous reverse proxy, what port numbers should I be using in the custom_rp.conf file?

 

[Rusty]

I've been getting errors, and cannot connect to the BitWarden, and I'm presuming it's a port problem, so I'm wondering given the settings that work in my previous reverse proxy, what port numbers should I be using in the custom_rp.conf file?

Have you tried using the same port numbers then?

 

[natrlhy]

What is the recommended way to upgrade bitwardenrs on Synology? I tried this:
Stop the container via Docker in DSM
Ran docker pull bitwardenrs/server:latest via SSH
Start the container via Docker in DSM

This doesn't seem to update bitwardenrs and I don't want to delete my working setup.

Thanks!

 

[Rusty]

What is the recommended way to upgrade bitwardenrs on Synology? I tried this:
Stop the container via Docker in DSM
Ran docker pull bitwardenrs/server:latest via SSH
Start the container via Docker in DSM

This doesn't seem to update bitwardenrs and I don't want to delete my working setup.

Thanks!

The last step is wrong. After you have downloaded the image do not start the container but use the Action menu and select the Clear command.

It will remove the container and create a new one with the new image. Do not panic when the container disappears. It will take a few seconds for the new one to appear.

After that start the container again

 

[natrlhy]

The last step is wrong. After you have downloaded the image do not start the container but use the Action menu and select the Clear command.

It will remove the container and create a new one with the new image. Do not panic when the container disappears. It will take a few seconds for the new one to appear.

After that start the container again

Thanks! That did it. Maybe add these upgrade steps to the main guide?

 

[Rusty]

Thanks! That did it. Maybe add these upgrade steps to the main guide?

Well update is a general Docker method and not specific to this guide but I see where you are coming from.

 

[SynoMan]

Bitwarden Selected As Best Password Manager By Us News And World Report

Bitwarden is an open source password management solution for individuals, teams, and business organizations.

bitwarden.com

 

[badtoast]

No, I did not setup email notifications.

Basically I did abit of read up on the netshoot.
After cross referencing with your thread as well,

I installed the container, ssh into the NAS.

through docker root, I could not perform nslookup.

root @ /
[1] → nslookup smtp.gmail.com
;; connection timed out; no servers could be reached

ip route show and ip neigh show are very barebone minimum as well.

so I decided to follow what @wwwampy suggested and go ahead to add the following in my NAS Firewall rule.

View attachment 1374


I went to the web portal of my BitWarden docker container,
All the ICONS are coming in and loading as intended.

icon_cache are loading the correct png file as well.

Thank you everyone.

@BlueBulb, I have been having the same issue as you where icons were not downloading. I just modified my firewall rules just as you indicated above now the icons have appeared!

THANK YOU for posing the question and posting the answer! Much appreciated.

 

[alisp]

Thanks Rusty for this guide. I just spent the weekend setting up bitwardenrs on my Synology. It was pretty frustrating with some trial and error. I got the basic installation working well, but wanted to enable the Live Sync feature and that's when I started having problems.

My main issue was getting the

.conf

file working and after a lot of trial and error, I realized it was this line:

server_name your_bitwarden_public_domain_name];

Removing the

]

after the public domain name fixed my issue of getting HTTPS errors. Since nobody else posted about this yet, I'm not sure if there was something else in my configuration that caused this or if this was just a typo. Hopefully that helps someone else here!

 

[Rusty]

Thanks Rusty for this guide

Your welcome.

Tnx for the heads up on this. That was definitely not supposed to be there, and I don't have it configured like that. Must have been an error when I was copying and altering the values.

Thank you for point this out

 

[alisp]

server_name your_bitwarden_public_domain_name];

Removing the

/

Not seeing an option to edit my previous post, but to make it clear, I meant the right bracket and NOT /. Oops!

 

[SynoMan]

Not seeing an option to edit my previous post

The time limit is set for editing posts to 4 hours.

I've edited the post now.

 

[Rusty]

Rusty updated BitWarden - self hosted password manager using vaultwarden/server image with a new update entry:

Docker image change

The old image bitwardenrs/server is being deprecated and changed with a new official one called vaultwarden/server.

The resource steps still apply.

Read the rest of this update entry...

 

[maravac]

Rusty updated BitWarden - self hosted password manager using vaultwarden/server image with a new update entry:

Docker image change



Read the rest of this update entry...

Ooops! So what should I do now, when I am using bitwardenrs/server and now it is not accessible anymore (via reverse proxy and custom domain/subdomain)? How to get it to work again and not to loose my data?
If there are some steps which can be done or in portainer or in Synology Docker, just let me know.
Thank you.

 

[Rusty]

If there are some steps which can be done or in portainer or in Synology Docker, just let me know

It is simple.

Start by downloading the new image. Then stop the current container and make a new one with the same settings but with a new image. Connect that new container to your current /data volume, and fire it up.

Everything will be the same and you will pick up where you left off. There are no major changes, its just the name that was changed (there was a lot of chatter on this on their Matrix chat channel in the past weeks).

More info on the current info and name change here - Release 1.21.0 · dani-garcia/vaultwarden

 

[SynoMan]

And after that you'll see this:

 

[maravac]

Great! Worked perfectly, thanks for help

-- post merged: 30. Apr 2021 --

btw. when I want to delete the older bitwardenrs/server container, should I also turn on the "automatically remove non-persistent volumes" or not?" To be humble, I have no glue what that means...

 

[paradeiser]

Then stop the current container and make a new one with the same settings but with a new image.

One simple way to achieve this is:

1. download the new "vaultwarden/server:latest" image
2. Select the old bitwarden container and export the current settings (menu on top) as a small .json file
3. open it in a code/text editor and change 3 lines:
   1. "cmd" : "/bin/sh -c ./bitwarden_rs", to "cmd" : "/bin/sh -c ./vaultwarden",
   2. "image" : "bitwardenrs/server:latest", to "image" : "vaultwarden/server:latest",
   3. "name" : "bitwarden-server", to "name" : "vaultwarden-server",
4. stop the old bitwarden container
5. edit the local port-settings of the old container (e.g. add +1 to the port numbers) to avoid port-collision
6. import the edited .json file
7. start up the new container

Optionally don't forget to turn off auto-restart for the old container.
For me, it worked like this - very easy (did I forget something?).

All the best,
paradeiser