How to Self-Host Vaultwarden Password Manager on a VPS [Complete Guide]

13 min read
How to Self-Host Vaultwarden Password Manager on a VPS [Complete Guide]
Summarize with:
Share:

To self-host Vaultwarden on a VPS, create an NGINX server, choose Vaultwarden in xCloud One Click Apps, and click Next. xCloud installs the app and requests the SSL certificate. Then create your account, close sign-ups, connect your Bitwarden apps, and run a backup you have tested by restoring it somewhere safe.

Vaultwarden uses very little memory, so the software has never been the hard part. The hard part is everything around it: a reverse proxy, a valid certificate, firewall rules, and backups you have actually restored.

Skip any of those and you end up with a password vault reachable over plain HTTP, open to public registration, with nothing to recover from. The container runs fine. The setup is a liability.

This guide takes the shortcut that removes most of that risk. Using xCloud One Click Apps, you deploy Vaultwarden onto an NGINX server with SSL issued automatically, then spend your remaining effort on the two things that genuinely protect a vault: closing registration and testing a restore. If you want background on the software first, read what Vaultwarden is and whether it is safe to self-host.

Table of Contents

TL;DR

  • 1 GB of RAM is enough for Vaultwarden. It uses very little memory. The Vaultwarden hosting page starts at 6 GB for $24.99/month.
  • One Click Apps provisions the container, Nginx, and the certificate, which removes the three steps people most often get wrong.
  • Use a custom domain, not a demo domain, for a real vault. Bitwarden clients need stable HTTPS.
  • Close registration the moment your own account exists.
  • Store your Admin Token somewhere safe. Vaultwarden’s published advisories include issues in the admin page.
  • Export an encrypted vault backup and keep it off the server, then confirm it imports.

What You Need Before Starting

RequirementDetails
An xCloud accountFree to create, no server required up front.
A serverEither a Cloud VPS from xCloud or your own VPS from DigitalOcean, Vultr, Hetzner, AWS, or Linode.
1 vCPU and 1 GB RAMComfortable for a household or small team. The Vaultwarden hosting page starts at 6 GB for $24.99/month.
A domain or subdomainFor example vault.example.com. Needed for a production vault.
DNS accessTo point an A record at the server.
A little timeMost of it is waiting for the server to provision.

No SSH keys, no Docker install, and no Certbot commands. If you are still weighing where to run this, our roundup of Vaultwarden hosting providers compares nine options, and the primer on how cloud hosting works covers the fundamentals.

Step 1: Create an NGINX Server

First, create the server that will run Vaultwarden. From the dashboard, click New Server and enter the credentials needed to connect.

You can deploy to your own server or to a Cloud VPS from xCloud. Choose your provider next. This guide uses a Cloud VPS from xCloud, though the flow is identical if you bring your own VPS through self-managed hosting.

Enter a Server Name, set the App Type to Vaultwarden, and add any Tags that will help you identify this server later. The App Type field is optional and only affects how the server is labeled.

Under Choose Web Server, keep NGINX selected: Vaultwarden runs as a container behind Nginx, xCloud installs Docker on the NGINX server for you, and OpenLiteSpeed servers cannot run Docker. Our explainer on Docker and its components covers what that stack is doing if the terms are unfamiliar.

Choose your server options and region, pick the plan that fits, then click Create. Vaultwarden needs very little memory. The Vaultwarden hosting page starts at 6 GB for $24.99/month.

Wait until the server reports as fully operational before deploying, since starting too early can leave services half-initialized.

Step 2: Go to One Click Apps and Choose Vaultwarden

From your dashboard, click One Click Apps and select Vaultwarden from the catalog. The same One Click Apps library holds other open-source tools, so the server you just built can host more than the vault.

Self-Host Vaultwarden Password Manager

Step 3: Set Up the Vaultwarden Application

On the site setup screen, enter a Site Title and add any Tags that help organize the deployment.

You will then see two deployment options. Go Live attaches your own custom domain, and Demo Site assigns a free xCloud demo domain instead.

For a password vault, choose Go Live with a custom domain. A demo domain is fine for evaluating Vaultwarden, but every Bitwarden client stores the server URL you log in with, so moving off a demo domain later means reconfiguring every device. Point an A record at your server, then enter the domain here. The demo site documentation 👉 covers the alternative if you only want to test.

Step 4: Deploy and Let SSL Issue

Click Next to start the deployment. xCloud installs Vaultwarden, connects it to your domain and requests a free SSL certificate.

This is the part that usually takes the most manual work. The reverse proxy configuration and the certificate are handled during this step. If you want to understand what is being configured, the Let’s Encrypt SSL guide 👉 walks through the manual equivalent.

Wait for the deployment to report success before continuing.

Step 5: Visit the Application

From the dashboard, click Visit Site to open your Vaultwarden instance.

You should land on the Vaultwarden login page over HTTPS with a valid padlock. If the certificate has not issued yet, wait and reload before assuming something went wrong.

Step 6: Complete the Vaultwarden Setup

Click Create account and set a strong master password. Nobody can reset this for you, so use a passphrase you will remember and keep a written copy somewhere physically secure.

After logging in, open Settings → Security → Keys and confirm the KDF is set to Argon2id. This is what protects you if an encrypted backup ever leaks, so it is worth checking rather than assuming.

Now close the door behind you. On the Environment page, change SIGNUPS_ALLOWED to false and click Save & Redeploy. Leave registration open and anyone who finds your domain can create an account.

One warning: Vaultwarden says settings saved on the /admin page override environment settings. If anyone has saved settings there, this change may do nothing, so try to create a test account in a private browser window to check it.

Two more settings worth deciding deliberately:

Decide what to do with the admin page. Vaultwarden’s published advisories include remote code execution and CSRF issues in the optional admin page. xCloud creates an Admin Token during install, so the page starts on. If you keep it, store the token somewhere safe. If you do not need it, follow Vaultwarden’s guide to turn it off.

Configure SMTP if you want invites. Organization invitations and password hints need mail credentials before they will send.

Step 7: Connect Your Bitwarden Clients

Vaultwarden speaks the Bitwarden API, so you use the official apps rather than anything custom.

  1. Install the Bitwarden app, browser extension, or CLI
  2. On the login screen, open the settings icon before signing in
  3. Set Server URL to your Vaultwarden domain
  4. Save, then log in with the account you created
  5. Import an existing vault from a JSON or CSV export if you are migrating

Do this on every device before you decommission whatever you are moving away from.

Step 8: Sort Out Backups

Your vault is only backed up once you set this up. Open Previous Backups on your site and click Backup Now, or turn on Automatic Backup in Backup Settings and choose how often it runs. Add a remote destination there to keep a copy off the server. xCloud’s backup screen says the app stops while its data is read, for seconds on a small app and longer on a large one. Docker app backups are not on the Free plan. Buying a Cloud VPS moves a Free team to the Starter plan, which includes them. This adds no charge beyond the Cloud VPS price. On your own server on the Free plan, you need to upgrade first.

Add one more layer that costs nothing. From the Vaultwarden web vault, export an encrypted JSON copy and store it somewhere off the server, such as an encrypted drive at home.

Then import that export into a throwaway account and confirm your entries arrive. A backup nobody has restored is a hope rather than a backup, and this test is what makes the rest of this setup trustworthy.

Common Problems and Fixes

SymptomCauseFix
Login page shows a certificate warningSSL still issuing, or DNS not propagatedConfirm the A record resolves, wait, then reload
Mobile app refuses to connectServer URL typed without https://Re-enter the full URL in client settings
Strangers registering accountsRegistration left openSet SIGNUPS_ALLOWED to false and redeploy
Invite emails never arriveSMTP not configuredAdd mail credentials in the app’s environment settings
Deployment fails immediatelyServer not fully provisionedWait for the server to report operational, then retry
Devices do not sync new entriesClient cached an old sessionLog out and back in on the affected device

Two more worth knowing. Vaultwarden releases sometimes state a minimum supported Bitwarden client version, so check your server version first if mobile logins break after an app update. And if you ever migrate to a different server, preserve the RSA key files from the data directory, since replacing them logs every user out. The project wiki documents both areas.

Would You Rather Do It Manually?

Nothing here is magic. Every step xCloud automated is one you can perform yourself: install Docker, write a compose file so the app is only reachable through your domain, not by server IP and port, configure Nginx with the right proxy headers, run Certbot, and write a backup script driven by cron.

That path takes longer the first time and gives you full control of every config file. It also makes you responsible for certificate renewal, container updates, and noticing when a backup job stops running. Your time is the line item people forget when comparing a subscription to a cheap VPS.

If you want the panel but prefer writing your own compose file, xCloud supports that too: 👉 how to deploy Custom Docker with xCloud. And whichever route you take, the server itself still needs attention, so our guide on maximizing VPS security is worth an hour of your time.

✅ One Click Apps suits you if❌ Manual setup suits you better if
You want the vault live todayYou enjoy running servers
Nobody on staff owns server maintenanceYou want control of every config file
A team depends on the vaultIt is a personal vault only
You would rather not renew certificates by handYou are learning Linux administration deliberately

Being straight about it: a bare VPS running Vaultwarden costs a few dollars a month, and a Cloud VPS from xCloud costs more. You are paying for the server setup, not the compute. You still run backups and updates. Our comparison of self-managed and managed hosting lays the trade-off out in full.

Ready to deploy? See Vaultwarden hosting plans and let xCloud set up the server and SSL.

Get Your Vault Running This Week

You now have a working path: an NGINX server, Vaultwarden deployed from One Click Apps, SSL issued automatically, registration closed, clients connected, and an encrypted export you have tested.

The steps that protect you are the unglamorous ones. Registration disabled, the admin page turned off or its token stored safely, an export stored somewhere else, updates applied when they ship. Those four decisions separate a vault you can rely on from one that quietly becomes a problem.

Set aside time this week to work through it, then run the restore test. That test is what turns self-hosting into something you can trust with every credential you own.

If you have found this blog helpful, feel free to subscribe to our blogs for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our Facebook community to share insights and engage in discussions.

Frequently Asked Questions

What are the minimum VPS requirements for Vaultwarden?

One vCPU, 1 GB of RAM, and 20 GB of disk is comfortable for a household or small team. The Vaultwarden hosting page starts at 6 GB for $24.99/month. Vaultwarden itself uses very little memory, so the headroom is for the operating system, Nginx, and file attachments rather than the vault.

Can I self-host Vaultwarden without a domain name?

Not for real use. Bitwarden’s mobile and desktop clients require a valid HTTPS certificate, and public certificate authorities do not issue them for bare IP addresses. An xCloud demo domain works for evaluation, but move to a custom domain before you store anything you depend on.

Do I need to know Docker to deploy Vaultwarden this way?

No. One Click Apps provisions the container, the Nginx configuration, and the certificate for you, so the deployment is a form rather than a terminal session. Understanding Docker helps when you want to change environment variables later, though it is not required to get running.

How do I add family members or teammates to my Vaultwarden server?

Create an organization from your account, then invite users by email from the organization’s Members tab. This works with registration disabled, which is the point of closing it. SMTP credentials need to be configured for those invites to send.

How often should I update Vaultwarden?

Check monthly, and immediately when a security advisory is published. The Vaultwarden repository publishes release notes with each version, and reading them takes two minutes. Some releases change the minimum supported client version, which is the usual cause of sudden mobile login failures.

Is a self-hosted Vaultwarden less secure than Bitwarden’s cloud?

The encryption model is identical, since your vault is encrypted on your device before it reaches any server. What differs is who handles operations, and an unpatched or unbacked-up server is a real risk that a hosted service absorbs for you. Our Vaultwarden and Bitwarden comparison covers this in detail.

What happens if my server dies? Can I recover my passwords?

Only if you have backups stored somewhere other than that server. App backups kept off the server plus an encrypted JSON export kept offline will get you back, and restoring means deploying Vaultwarden again and importing. Without either, the vault is unrecoverable, which is why the test in Step 8 matters more than any other step here.

Can I move my Vaultwarden instance to another host later?

Yes. Export an encrypted JSON copy from the web vault, deploy Vaultwarden on the new host, and import it there, then update the server URL in each client. If you have file access on both ends, copying the entire data directory preserves users and organizations as well. Broader hardening advice lives in our web hosting security best practices guide.

The same server-ownership tradeoffs apply to automation platforms; see our guide to hosting n8n on your own server.

Last updated November 3, 2026

← All articles