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

Last edited:
For the more timid... Stop the bitwardenrs container, then copy the /docker/bitwarden/data folder to /docker/vaultwarden/data. Point /docker/vaultwarden/data (external) to /data (internal).

Assign an external port to internal port 80, and update your reverse proxy to point to the vaultwarden port, and then launchthe new container!

Sync to confirm all is connected.
 
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...
You can yes. Bw doesn’t have any but yes you can
 
No, apart from the name and the image itself, nothing. You can use your existing volumes with this image.

yes I have made the switch over. The only thing I had to do was create a new container. I had to refer back to the resource to make sure all steps were properly configured. Stuff like this I have to create my own reference and throw it in a word doc, in case I need it in a pinch.
 
Hi @Rusty, thanks a lot for your effort here!
Vaultwarden 2.23.0 is still running like a charm.

I just wonder:
What's the most elegant way to achieve a redirect from http to https?

I've set up websocket LiveSync like described here.
Some browsers (Firefox) redirect http://mybitwarden.url to https://mybitwarden.url like expected.
But some browsers (Safari) redirect http://mybitwarden.url to https://myNAS.url:port

This corresponds to my settings in "Control Panel": Redirect for my DSM interface is turned on.
But how do I achieve the redirect for my specific bitwarden.url?

Using this tutorial (installing web station etc.) or is there a better/easier?

Thanks a lot,
marko
 
redirect from http to https?
Best way imho would be to use a proper reverse proxy. I use NPM docker image for this and by default it redirects http to https for all my apps. Ofc, you will have to have 80 and 443 open at the same time for this, but still, it works.

 
Hi, I've just updated the vault warden image to the last one (2.23.0) via Portainer. Everything goes well, and when I launch the address fort the graphical interface it appears without problem (it's http://192.168.1.109:32769).
I put e-mail address and the password, and I receive an error message: "This browser requires https to use the web vault. Check the Vaultwarden wiki for details on how to enable it".

Have I change something in the docker configuration? External access via Synology Reverse Proxy works fine, and redirect my "xxxx.synology.me:443" to the local "http://192.168.0.109:32769".

Thanks in advance.
 
Hi, I've just updated the vault warden image to the last one (2.23.0) via Portainer. Everything goes well, and when I launch the address fort the graphical interface it appears without problem (it's http://192.168.1.109:32769).
I put e-mail address and the password, and I receive an error message: "This browser requires https to use the web vault. Check the Vaultwarden wiki for details on how to enable it".

Have I change something in the docker configuration? External access via Synology Reverse Proxy works fine, and redirect my "xxxx.synology.me:443" to the local "http://192.168.0.109:32769".

Thanks in advance.
You can’t access bw without a valid https url regardless where you are accessing it from.
 
Hi, I've just updated the vault warden image to the last one (2.23.0) via Portainer. Everything goes well, and when I launch the address fort the graphical interface it appears without problem (it's http://192.168.1.109:32769).
I put e-mail address and the password, and I receive an error message: "This browser requires https to use the web vault. Check the Vaultwarden wiki for details on how to enable it".

Have I change something in the docker configuration? External access via Synology Reverse Proxy works fine, and redirect my "xxxx.synology.me:443" to the local "http://192.168.0.109:32769".

Thanks in advance.

Can you try HTTPS://192.168.1.109:32769 you'll get a cert error because its not a registered domain name, but you should be able to click advanced (depending on browser) and proceed with the connection
 
You can’t access bw without a valid https url regardless where you are accessing it from.

I’ve tried to use https://192.168.1.109:32769, but it doesn’t work. It’s a bit annoying not to access to the local Bitwarden server…
-- post merged: --

Can you try HTTPS://192.168.1.109:32769 you'll get a cert error because its not a registered domain name, but you should be able to click advanced (depending on browser) and proceed with the connection

I’ll try with another browser, because using Safari the https local url gives me an error without possibility to continue.
 
I’ve tried to use https://192.168.1.109:32769, but it doesn’t work. It’s a bit annoying not to access to the local Bitwarden server…

Actually when accessing it internally make sure you use the local bw port. If port 32769 is the external port, which is forwarded to your internal port it won’t work.

@Rusty I know this would work for synology. Maybe bw is different
 
That's an outdated image. Use Vaultwarden. It works with all Bitwarden apps.
The guide has modifications reflecting the image change (just not the screenshots).

Hi Rusty, will this setup work with the Apple iOS Bitwarden app, or is there any additional steps to follow please? Thank you
Yes it works fine with the latest official mobile app. Dev team uses the official code for this fork to maintain the compatibility. There was never any problem with it.
 
Last edited:
How are you guys backing up Bitwarden (Vaultwarden image)? Is it safe to use hyper backup or snapshot replication to take snapshots considering its a sqlite3 database? Or are you doing backups through the admin page "Backup database?"
 
I periodically go into Docker and EXPORT the container into a subdirectory in my Docker shared folder. And, I use hyperbackup to back up the entire Docker shared folder (which includes all the data, settings, etc for all my docker containers/applications) to another NAS every two hours.
 

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,413
I'll delete everything I can containers/images/etc, and start fresh over the weekend. While I really like...
Replies
48
Views
6,500
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
9,731
I ran across a very complete how-to-install-nextcloud on Docker using the Synology UI (just the UI, not...
Replies
28
Views
8,209
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,213
I discovered if you use fireflyiii/core:latest everything works just fine
Replies
35
Views
16,723

Welcome to SynoForum.com!

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

Registration is free, easy and fast!

Back
Top