How can we help?

The most common setup mistake is leaving the app pointed at Bitwarden's cloud instead of this public Vaultwarden server. Each app must be configured separately.

1. Open the app's login or registration screen.
2. Choose Self-hosted from the server selector. In browser and mobile apps it is usually called Logging in on; in the desktop app it is usually Accessing.
3. Enter this exact base URL, including HTTPS: https://vault.vaultwarden.net.
4. Save the setting, then enter your account email and master password.

Do not enter the web app's full path or add /#/login. Use the base server address above. Menu labels can change between app versions.

See the Bitwarden client environment guide for current app-specific screenshots.

Sync requires a working connection to the configured server. A client may also need to be unlocked before it can refresh data.

• Check that the device is online and can open the vault web app.
• Confirm the client is configured for https://vault.vaultwarden.net, not bitwarden.com or bitwarden.eu.
• Run a manual sync from the client's vault or account menu.
• Check the item exists in the web vault. If it exists only on one device, do not uninstall or clear that app's data before exporting or recovering the item.
• For browser autofill, confirm the extension is enabled, the item has the correct website URI, and the browser has granted the extension access to the page.

Sync is not the same as a backup. A deletion or mistaken edit may propagate to your other devices.

Useful official guidance: Sync your vault and browser autofill.

First make sure the app is pointed at the correct server URL and that you are using the email address associated with this instance.

The operators cannot recover or reset a forgotten master password. The master password protects the encryption keys for your vault; support staff cannot read it back or derive it from your account.

Before creating a new account, check every device and browser where you may still be logged in. If an app can still unlock using a previously configured PIN or biometric method, export or manually recover your vault data from that device. An emergency contact or another recovery mechanism can only help if it was configured beforehand and is supported by this account.

If you can sign in but believe the account is disabled or registration is unavailable, contact the instance operators. Do not create repeated accounts to work around a service-side restriction.

Further reading: Forgot master password.

Try another two-step method you already enabled, such as an authenticator app, hardware key or recovery code. Keep recovery codes somewhere separate from your password vault.

If all methods are unavailable, check whether you are still signed in on another device. The instance administrators can remove the two-step-login configuration from an account when necessary. This removes that second factor; it does not recover a forgotten master password, decrypt the vault or restore lost data. Contact admin@obco.pro from the email address registered to the account. Never send a one-time code, recovery code, API key or master password.

Set up more than one second-factor method where the client and server support it. See two-step login setup and lost-device recovery options.

Import: export your old password manager to a supported file format, open the vault and choose Tools → Import. Select the correct source format and upload the file. Imports may create duplicates if you import the same data twice. Review the result before deleting the source data.

Backup: open Tools → Export in the web vault. Choose My vault and .json (Encrypted) → Password protected when you need an encrypted export that can be imported to a different account or server. Store the export password separately from the file. An account-restricted export is tied to the original account and is not suitable for moving to a new server.

A plain CSV or unencrypted JSON export contains readable passwords. Avoid email or shared folders, protect it while in use and securely delete temporary plaintext exports after import.

Individual vault exports do not automatically include organization-owned data. Export organization data separately if you have the relevant permissions.

References: Import data, Export vault data and Encrypted exports.

Vaultwarden's upstream implementation lists support for personal vaults, attachments, Bitwarden Send, organizations, multi-factor authentication and emergency access. This does not mean every feature is enabled on this particular instance or available in every client.

• Attachments: upload limits may be set per user or organization. If an upload fails, check the file size and ask support whether a server limit applies.
• Bitwarden Send: the server can disable Sends or limit storage. File Sends may have additional account or client restrictions; text Sends and file Sends are not interchangeable.
• TOTP codes: authenticator-code generation is a client feature; availability and plan restrictions can vary by app.
• Organizations: sharing depends on whether organizations and invitations are enabled, membership permissions and the specific feature implemented by the server.
• Emergency access: configure trusted contacts in advance and confirm the feature is enabled; it cannot be arranged after an emergency has already occurred.

For current upstream implementation scope, check the Vaultwarden project README. For Bitwarden client feature details, see the Bitwarden Help Center.

Some clients keep local data, but offline behavior differs. Keyguard is a third-party Bitwarden-compatible app that supports connecting to a custom Vaultwarden server and keeps a local copy of the vault. After the first successful sync, it can show cached items without a connection.

Offline editing is available in Keyguard, but it is a paid feature on some builds, including the Google Play Android build. Check Keyguard's current licensing page for the build you use. When offline editing is available, changes remain local and sync back when the app is online again.

Offline access only applies to data already stored on that device. It does not make the server, new server-side changes or your other devices available during an outage. Keyguard is independent software, not an official Bitwarden or Vaultwarden client.

Learn more: Connect Keyguard to a self-hosted server, offline access and Premium feature limits.

You can ask for your account to be deleted by emailing admin@obco.pro from the email address registered to the account. No reason is required and we do not ask why you want to leave. Export any vault data you want to keep before requesting deletion. Never send your master password or recovery codes.

To keep the service maintained, accounts that appear unused or contain no vault data may also be removed as part of routine service maintenance. No fixed cleanup schedule is published. Data removed from the active service may remain in existing backups until those backups expire through the normal backup rotation; deletion from the live database does not mean every backup copy disappears immediately.

Compatible Bitwarden clients encrypt vault contents on your device before synchronising them. The normal Vaultwarden admin interface cannot decrypt vault items, read plaintext passwords or reset a master password. Administrators can manage accounts, remove a user's two-step-login configuration and see basic account metadata such as email address, creation date and account status.

Infrastructure operators still control the server, deployment, encrypted files, backups and operational systems. The service therefore remains a third-party host that you must trust to run the expected software and protect stored data. Keep your own encrypted export and never share your master password with support.

The service Privacy Notice explains what personal data is processed, why it is needed, relevant provider categories, retention criteria and how to exercise your rights. For account deletion, see Deleting your account.

For instance-specific problems, email admin@obco.pro. Include the client name and version, device operating system, the exact error text and when the issue started. Never include passwords, recovery codes, API keys, vault exports or screenshots containing secrets.

The operators can help with service status, registration, the server URL, account administration questions and service-side faults. Support is best-effort; no response-time commitment is published. On Discord, the community contact name is Yonggan.

They cannot retrieve a forgotten master password, decrypt your vault or restore data that is not available in the service or a usable backup. For bugs in Vaultwarden itself, consult the upstream project guidance; do not send Vaultwarden server bugs to Bitwarden's official support channels.