Self-hosting Vaultwarden: a password manager on your own server
5 min read
Vaultwarden is a small Bitwarden-compatible server that runs in about 10 MB of memory. How to start it with Docker, why HTTPS is not optional, how to close sign-ups, what to back up and how to update. Tested with Vaultwarden 1.37.
Vaultwarden is a server for the Bitwarden apps: the browser extensions, the desktop apps and the phone apps all work with it. It is written in Rust and is very small. A password manager is also the one service where a mistake hurts most, so this guide is short on installation and long on what comes after.
We tested the commands here on 12 November 2026 with the official image: Vaultwarden 1.37.5 with web vault 2026.10.1.
In short
- One container, one volume (
/data), no database server. - It is tiny: our idle container used about 8 MB of memory.
- HTTPS is required. The web vault does not work over plain HTTP.
- After creating your account, set
SIGNUPS_ALLOWED=false. - The admin page is off unless you set
ADMIN_TOKEN. Leave it off if you do not need it. - Back up
/dataand test the restore. Your passwords are in there.
1. Start the container
docker volume create vw_data
docker run -d --name vaultwarden --restart unless-stopped \
-p 127.0.0.1:8080:80 \
-e DOMAIN=https://vault.example.com \
-e SIGNUPS_ALLOWED=true \
-v vw_data:/data \
docker.io/vaultwarden/server:1.37.5
127.0.0.1:8080: reachable only from the server itself. The web server in front adds HTTPS.DOMAIN: the public address, withhttps://. Vaultwarden uses it in links and for attachments.- A fixed version tag rather than
:latest, so that updates happen when you decide.
Check that it runs:
curl -s -o /dev/null -w '%{http_code}\n' http://127.0.0.1:8080/alive
200
2. HTTPS is not optional
The Bitwarden web vault does its encryption in the browser, and browsers allow that only on secure pages. Over plain HTTP you can load the page but not create an account.
Put nginx in front:
server {
server_name vault.example.com;
location / {
proxy_pass http://127.0.0.1:8080;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
}
}
and get a certificate before you do anything else.
3. Create your account, then close the door
Open the site and create your account. Choose a long master password: it is the key to everything, and nobody can reset it for you. Vaultwarden never sees it.
Then stop new registrations. Recreate the container with:
-e SIGNUPS_ALLOWED=false
Until you do this, anybody who finds the address can create an account on your server. To add family or team members later, invite them from an organisation, or open sign-ups for a moment.
Turn on two-step login for your account in the web vault settings.
4. The admin page
/admin is a settings page for the whole server. In our test it answered:
The admin panel is disabled, please configure the 'ADMIN_TOKEN' variable to enable it
That is the safe default. If you need it (to invite users, or to see settings), set ADMIN_TOKEN to a long random value, and consider allowing /admin from your IP address only.
5. What is in the volume
db.sqlite3 rsa_key.pem tmp ...
db.sqlite3: all users and their encrypted vaults.rsa_key.pem: the key that signs login tokens.attachments/andsends/appear when those features are used.
The vault entries are encrypted with each user's master password before they reach the server. Somebody who steals the database still has to break that password, which is why it should be long.
6. Backups
This is the most important section. A lost vault means every password in it is gone.
docker stop vaultwarden
docker run --rm -v vw_data:/data -v "$PWD":/backup alpine \
tar czf /backup/vaultwarden-$(date +%F).tar.gz -C /data .
docker start vaultwarden
- Run it daily and copy the archive to storage outside the server.
- Keep several days of copies, not only the newest one.
- Restore one into a test container and log in. A backup that was never restored is not yet a backup.
- Also export your vault from the app now and then, and keep the encrypted export somewhere safe.
The Bitwarden apps keep a local copy of the vault, so a short outage of the server does not lock you out. A lost server without a backup still does.
7. Updates
docker pull docker.io/vaultwarden/server:<new version>
docker stop vaultwarden && docker rm vaultwarden
# run the same docker run command with the new tag
Take a backup first. Follow the project's releases: security fixes for a password manager should not wait.
8. Reduce what is exposed
- Keep the server itself updated, with a firewall that opens only 80 and 443.
- If only you use the vault, restrict the site to your own IP addresses or a VPN.
- Watch the web server's log for repeated failed logins.
With Zefily
Vaultwarden is a one-click app in Zefily: a rootless container under the site's own Linux user, on 127.0.0.1 behind the web server with HTTPS, with its data in a volume that survives updates. DOMAIN is set for you. Afterwards you create your account, set SIGNUPS_ALLOWED=false in the site's .env and press Deploy now. Backups to your own storage and access rules by IP address are part of the panel. See Container apps and Backups.
Frequently asked questions
Is Vaultwarden compatible with the Bitwarden apps?
Yes. The official Bitwarden browser extensions, desktop apps and mobile apps work with a Vaultwarden server; you enter your own server address when logging in.
How much memory does Vaultwarden need?
Very little. Our idle Vaultwarden 1.37.5 container used about 8 MB of memory.
Does Vaultwarden work without HTTPS?
No. The web vault needs a secure page to do its encryption in the browser. Put the container behind a web server with a certificate.
How do I stop strangers from signing up on my Vaultwarden?
Set SIGNUPS_ALLOWED=false and restart the container after you have created your own account.
What do I need to back up for Vaultwarden?
The whole /data volume: db.sqlite3, rsa_key.pem and the attachments. Copy it off the server daily and test a restore.
See Access, caching and protection for restricting a site by IP address in Zefily.