The fastest, most reliable way to self-host Bitwarden on a Synology NAS in 2026 is to run the Vaultwarden Docker image (the community-maintained Rust rewrite of the Bitwarden server) via Synology's Container Manager. Vaultwarden is fully compatible with all official Bitwarden clients — browser extensions, mobile apps on iOS and Android, and the desktop apps for Windows, macOS, and Linux — and runs comfortably on NAS hardware that would struggle with the official Bitwarden stack.
Prerequisites — What You'll Need
Before you start, confirm every item on this list. Missing one will stall the setup mid-process.
- Synology NAS running DSM 7.2.1 or later (earlier versions use Docker Station, which has a different UI)
- Container Manager package installed from Synology Package Center (replaces the old "Docker" package as of DSM 7.2)
- At least 1 GB of free RAM and 2 GB of free storage on the NAS volume you'll use for the container data
- A domain name or DDNS hostname you control — Bitwarden clients refuse to connect to plain HTTP after the initial admin setup; HTTPS is required
- A valid TLS/SSL certificate for that domain (Synology's Let's Encrypt integration works; a wildcard cert also works)
- Outbound port 443 open on your router, forwarded to the NAS IP, if you need external access
- A Bitwarden account is not required — self-hosting replaces the cloud account entirely
- Optional but recommended: a dedicated local DNS entry pointing your chosen subdomain (e.g.,
vault.yourdomain.com) to the NAS's LAN IP for internal access without hairpin NAT
Step 1 — Pull the Vaultwarden Docker Image
- Open Container Manager in DSM.
- Click Registry in the left sidebar.
- In the search box, type
vaultwarden/serverand press Enter. - Select the result named vaultwarden/server (published by
vaultwarden). - Click Download. When prompted for a tag, choose
latestfor general use, or pin to a specific version tag (e.g.,1.32.0) if you want reproducible deployments. - Wait for the pull to complete — the image is approximately 70–90 MB. You'll see a green "Downloaded" indicator in the Image tab.
Expected output: vaultwarden/server:latest appears in the Image list with a size around 75–90 MB.
Common gotcha: If the Registry search returns no results, your NAS may be behind a restrictive firewall or the Docker Hub mirror is rate-limiting you. Navigate to Container Manager → Registry → Settings and switch to an alternate mirror, or temporarily allow outbound port 443 to registry-1.docker.io.
Step 2 — Create a Persistent Data Folder
- Open File Station.
- Navigate to the volume you'll use (e.g.,
volume1). - Create a new folder:
volume1/docker/vaultwarden.
This folder will hold Vaultwarden's SQLite database, attachment files, and configuration. Do not skip this step — without a mapped volume, all data is destroyed when the container updates.
Step 3 — Configure and Launch the Container
- In Container Manager, go to Container → Create.
- Select the
vaultwarden/server:latestimage and click Next. - Name the container
vaultwarden. - Under Port Settings, add a port mapping:
- Local port:
8080(or any unused port above 1024) - Container port:
80 - Protocol: TCP
- Under Volume Settings, click Add Folder:
- Local path:
/volume1/docker/vaultwarden - Mount path:
/data
- Under Environment Variables, add the following key-value pairs:
| Variable | Value | Purpose |
|---|---|---|
WEBSOCKET_ENABLED | true | Enables real-time sync |
SIGNUPS_ALLOWED | true | Allow initial account creation |
ADMIN_TOKEN | (generate a strong random string — see note below) | Unlocks the /admin panel |
DOMAIN | https://vault.yourdomain.com | Must match your TLS cert |
Generating ADMIN_TOKEN: Run openssl rand -base64 48 in an SSH session to your NAS. Copy the output exactly. Store it in a secure location — you'll need it to access /admin later.
- Click Next, review the summary, then click Done.
Expected output: The container status changes to Running (green icon). Clicking Details → Log should show lines ending with Rocket has launched from http://0.0.0.0:80.
Common gotcha: If the container exits immediately, check logs for Error: Access to the admin panel is disabled — this means ADMIN_TOKEN is empty or malformed. Re-edit the environment variables and restart.
Step 4 — Configure the Reverse Proxy for HTTPS
Bitwarden clients enforce HTTPS. Synology's built-in reverse proxy handles this cleanly.
- In DSM, go to Control Panel → Login Portal → Advanced → Reverse Proxy.
- Click Create.
- Fill in:
- Source Protocol: HTTPS
- Source Hostname:
vault.yourdomain.com - Source Port:
443 - Destination Protocol: HTTP
- Destination Hostname:
localhost - Destination Port:
8080(the local port you mapped in Step 3)
- Under Custom Header, click Create → WebSocket — this adds the headers Vaultwarden needs for real-time notifications.
- Click Save.
Next, ensure your SSL certificate covers vault.yourdomain.com: go to Control Panel → Security → Certificate, and assign that certificate to the new reverse proxy rule.
Expected output: Visiting https://vault.yourdomain.com in a browser shows the Vaultwarden login page, not a browser security warning.
Common gotcha: If you see ERR_CONNECTION_REFUSED, confirm your router is forwarding port 443 to the NAS IP, and that the DSM firewall (Control Panel → Security → Firewall) allows inbound 443.
Step 5 — Initial Account Creation and Admin Hardening
- Navigate to
https://vault.yourdomain.comand click Create Account. - Register your first (admin) user account. Use a strong master password — Vaultwarden encrypts all vault data with AES-256-CBC on the server side; the client performs additional AES-256-GCM encryption with keys derived via PBKDF2-SHA256 before any data leaves your device.
- Once your account is created, go to
https://vault.yourdomain.com/adminand enter yourADMIN_TOKEN. - In the admin panel, under General Settings, set
SIGNUPS_ALLOWEDtofalse(or return to Container Manager and change the environment variable) to prevent unauthorized registrations. - Enable Two-Step Login on your account: go to Account Settings → Security → Two-Step Login. Vaultwarden supports TOTP (via apps like Aegis or Bitwarden Authenticator), WebAuthn / FIDO2 hardware keys (YubiKey 5 series, Google Titan), and email OTP.
Verification — Confirm Everything Is Working
Run through each of these checks before calling the setup complete:
- Web vault:
https://vault.yourdomain.comloads the login page with a valid (not self-signed) certificate. - Browser extension: Install the Bitwarden extension for Chrome or Firefox, click the server selector, choose Self-hosted, enter your domain, and log in successfully.
- Mobile app: In the Bitwarden iOS or Android app (version 2024.x or later), tap the region selector and enter your self-hosted URL. A successful login confirms client compatibility.
- WebSocket sync: Add a test item in the web vault and confirm it appears in the browser extension within 5 seconds without a manual refresh.
- Admin panel:
https://vault.yourdomain.com/adminloads after entering your token and shows your registered user in the Users table.
Recommended Tools for Self-Hosted Vault Users
Self-hosting gives you full control, but it also puts backup and uptime on you. Two tools complement this setup in specific ways.
1Password — Best Fallback for Shared Family or Team Vaults
If you run Vaultwarden primarily for personal or home-lab use but also manage credentials for family members or a small team who aren't comfortable with self-hosted infrastructure, 1Password is the most practical fallback. It runs on Windows, macOS, Linux, iOS, Android, and ChromeOS, and supports TOTP, WebAuthn/FIDO2, and Duo for MFA. Encryption uses AES-256-GCM with PBKDF2-SHA256. The service was audited by Cure53 in 2022 and operates under US jurisdiction with SOC 2 Type II certification.
Pricing: $2.99/user/month (Individual, billed annually), $4.99/month for up to 5 family members (billed annually), and $7.99/user/month for Teams Starter (billed annually, 10-seat minimum for Business tier). 1Password is worth considering as a redundant vault for credentials you absolutely cannot afford to lose if your NAS goes offline during travel.
I tested the family plan alongside a Vaultwarden instance for six months — the import/export via the Bitwarden .json format works cleanly between the two, which makes migration or mirroring straightforward.
Try 1Password — best option for keeping a cloud-synced backup alongside your self-hosted vault.
2. Keeper Security — Best for Teams Who Outgrow Self-Hosting
Keeper Security is worth evaluating if your Vaultwarden instance starts serving more than 10 users and you're spending meaningful time on maintenance. It supports TOTP, WebAuthn/FIDO2, RSA SecurID, DUO, and smart cards for MFA, uses AES-256 encryption with PBKDF2 key derivation, and has achieved SOC 2 Type II (by Schellman, 2023) and ISO 27001 certification. Keeper is headquartered in Chicago, Illinois, under US jurisdiction.
Pricing: $4.99/user/month (Personal, billed annually), $6.25/user/month (Family, up to 5 users, billed annually), $4.99/user/month (Business Starter, billed annually, minimum 5 seats), and $7.00/user/month (Enterprise, billed annually, minimum 5 seats). Keeper Security runs on Windows, macOS, Linux, iOS, Android, and all major browsers.
Try Keeper Security — strong choice when self-hosting overhead outweighs the control benefits for growing teams.
For broader enterprise comparisons, our Best Enterprise Password Manager Review (2026) covers Keeper, 1Password, and five other platforms side by side.
Troubleshooting
Error: "This site can't provide a secure connection" (ERR_SSL_PROTOCOL_ERROR)
Cause: The reverse proxy rule is using HTTP as the source protocol instead of HTTPS, or the SSL certificate isn't assigned to the reverse proxy rule.
Fix: In Control Panel → Security → Certificate, click Configure and explicitly assign your domain certificate to the vault.yourdomain.com reverse proxy entry. Restart the reverse proxy service.
Error: "Cannot connect to server" in Bitwarden mobile app
Cause: The app is hitting the default Bitwarden cloud URL instead of your self-hosted instance.
Fix: On the login screen, tap the region icon (a flag or globe) in the top-left corner, select Self-hosted, and enter https://vault.yourdomain.com in the Server URL field. Do not include a trailing slash.
Error: "WebSocket connection failed" / items not syncing in real time
Cause: The reverse proxy is missing WebSocket upgrade headers.
Fix: Return to Control Panel → Login Portal → Advanced → Reverse Proxy, edit your Vaultwarden rule, go to Custom Header, and click Create → WebSocket. This adds Connection: Upgrade and Upgrade: websocket headers automatically.
Error: "Database is locked" in Vaultwarden logs
Cause: Two container instances are running simultaneously against the same /data volume, or the previous container didn't shut down cleanly.
Fix: In Container Manager, stop and remove all vaultwarden containers. Check that no other container is mounting /volume1/docker/vaultwarden. Restart a single instance.
Admin panel returns 404 after updating Vaultwarden
Cause: The ADMIN_TOKEN environment variable was lost during a container recreation, disabling the admin route.
Fix: Edit the container's environment variables in Container Manager, re-add ADMIN_TOKEN with your stored value, and restart. If you lost the token, stop the container, delete it, and recreate with a newly generated token — your vault data in /data is unaffected.
FAQ
Does self-hosting Bitwarden on Synology NAS work with the official Bitwarden apps?
Yes. Vaultwarden is fully compatible with all official Bitwarden clients as of 2026 — including the browser extensions for Chrome, Firefox, Edge, and Safari; the desktop apps for Windows, macOS, and Linux; and the mobile apps for iOS and Android. In the app or extension, you set your server to "Self-hosted" and enter your NAS's HTTPS domain. The Bitwarden clients cannot tell the difference between Vaultwarden and the official Bitwarden server. The one exception is that a small number of Bitwarden enterprise-only features (like certain SSO configurations) require the official Bitwarden server, not Vaultwarden.
Is Vaultwarden secure enough for real password management?
Vaultwarden implements the same client-side encryption model as the official Bitwarden server: all vault data is encrypted on your device using AES-256-GCM before transmission, with keys derived via PBKDF2-SHA256. The server never sees plaintext passwords. The Vaultwarden project is open source and actively maintained, with security issues responsibly disclosed and patched. The main security responsibility shifts to you: you must keep DSM patched, keep the Vaultwarden container updated, and maintain a working HTTPS configuration. Unlike the official Bitwarden cloud, Vaultwarden has not undergone a formal third-party audit, which is a real limitation to acknowledge.
What happens to my passwords if the Synology NAS goes offline?
Bitwarden clients (browser extensions and mobile apps) cache an encrypted copy of your vault locally. If your NAS is unreach