Skip to content

Vaultwarden (Bitwarden-compatible password Manager)

This document explains how Vaultwarden is deployed, accessed, and managed when installed as a One‑Click App on FlyWP.

Vaultwarden is a lightweight, open‑source, Bitwarden‑compatible password manager server. It supports all official Bitwarden clients while consuming significantly fewer resources than the official server.

FlyWP provides Vaultwarden as a one‑click deployment, handling installation, web server configuration, SSL, and environment variables automatically.

When you deploy Vaultwarden from Create Site → Deploy One Click App → Vaultwarden, FlyWP automatically:

  • Provisions Vaultwarden on the selected server
  • Assigns a temporary FlyWP subdomain
  • Configures NGINX and SSL
  • Generates a secure admin token
  • Exposes required environment variables

No manual Docker or system setup is required.

After deployment, two interfaces are available:

  • Vaultwarden User Interface
    https://<your-domain>/
  • Vaultwarden Admin Panel
    https://<your-domain>/admin

The admin panel is protected by an admin token.

FlyWP configures Vaultwarden primarily through environment variables. These can be viewed and updated from:

Site → Environment

Terminal window
DOMAIN=https://your-domain
ADMIN_TOKEN=<generated-token>
SIGNUPS_ALLOWED=true
  • DOMAIN
    Public base URL of your Vaultwarden instance. Must match the site domain and protocol.
  • ADMIN_TOKEN
    Token required to access /admin. This is generated automatically during deployment.
  • SIGNUPS_ALLOWED
    Controls whether new users can self‑register.
    • true → anyone can sign up
    • false → only invited users can register

After changing environment variables, always click Update Environment.

  1. Visit:https://<your-domain>/admin
  2. Enter the ADMIN_TOKEN from the Environment page
  3. Click Enter

If the token is correct, you will be logged into the Vaultwarden Admin UI.

Vaultwarden supports configuration via:

  • Environment variables (preferred)
  • Admin UI settings

Admin UI settings override environment variables once saved.

In the admin UI:

  • Overridden values are highlighted with a yellow background
  • Read‑only values can only be set via environment variables
  • Use environment variables for infrastructure‑level configuration
  • Avoid mixing the same settings between UI and environment variables

From the Admin Panel you can configure:

  • User and organization management
  • Email / SMTP settings
  • 2FA policies
  • YubiKey and Duo integration
  • OpenID Connect (SSO)
  • Database backup
  • Diagnostic information

These settings are applied immediately after saving.

  • SSL is enabled automatically via FlyWP
  • Admin panel is protected by token authentication
  • HTTPS is enforced if the domain supports SSL
  • Rotate the ADMIN_TOKEN after initial setup
  • Disable public signups once users are created
  • Use a custom domain instead of the default FlyWP subdomain
  • Enable SMTP and email verification

From the FlyWP dashboard:

  • Manage → Restart, stop, or redeploy the service
  • Logs → View application and error logs
  • NGINX Config → Advanced routing or headers (use cautiously)

Vaultwarden stores data in an internal database.

Available options:

  • Manual backup from Admin Panel → Backup Database
  • Server‑level backups via FlyWP (recommended)

Always test restores before relying on backups.

  • Ensure /admin is appended to the domain
  • Verify ADMIN_TOKEN is correct
  • Confirm the DOMAIN variable matches the URL
  • Check if the setting is overridden in Admin UI
  • Restart the service after major config changes
  • Confirm SIGNUPS_ALLOWED=true
  • Check email/SMTP configuration

Vaultwarden One‑Click App is ideal for:

  • Personal password management
  • Small teams and startups
  • Self‑hosted security‑focused setups
  • Low‑resource servers

Not recommended for very large enterprises without custom scaling.

FlyWP’s Vaultwarden One‑Click App provides:

  • Fast deployment
  • Secure defaults
  • Minimal maintenance
  • Full Bitwarden client compatibility

Configuration should be done primarily through environment variables, with the admin UI used for operational control only.

Still stuck? How can we help?