Skip to content

Vaultwarden / Bitwarden — FAQ

vault.saxobroko.com — fix the vault before almost any other login.

VLT-001 — What is Vaultwarden?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Self-hosted password manager at vault.saxobroko.com on TrueNAS.
  2. Stores bank, insurance, Authentik, Cloudflare, homelab logins. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-002 — Server URL for all clients?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. https://vault.saxobroko.com — set before first login in every app. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-003 — Invalid master password?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Caps Lock, copy from handover, try web vault, stop after 3 tries. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-004 — Create new Bitwarden account?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. No — new account is empty. Use Saxon's existing account. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-005 — YubiKey required but fails?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Desk USB key, portable NFC key, try other key, check PIN — YubiKey FAQs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-006 — Forgot master password?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Search handover + recovery codes. Do not wipe NAS. Ask Ryan. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-007 — Vault site won't load?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Test internet, another device, NAS may be off — internet broken guide. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-008 — Unlock vs login?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Login = new device + 2FA. Unlock = master/PIN on already logged-in app. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-009 — Server location?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. TrueNAS 192.168.2.203 — PC is client only. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-010 — Official Bitwarden apps OK?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Yes with self-hosted URL — not bitwarden.com cloud. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-011 — Find MyState login?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Search MyState — Login MyState. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-012 — Find Vanguard login?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Search Vanguard — Login Vanguard. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-013 — Folders meaning?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Organize entries — search finds everything regardless. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-014 — Phone not syncing?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Check self-hosted URL, refresh, vault server must be up. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-015 — Browser extension locked?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Enter master password or PIN/biometric. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-016 — Should I export backup?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Yes — encrypted export offline periodically. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-017 — Restore from export?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Tools → Import — Ryan handles server DB restore if needed. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-018 — Admin panel?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Server admin — Ryan only, token in vault. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-019 — TOTP codes in vault?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Yes — authenticator on login entries. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-020 — Share one account?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Not recommended — separate users better. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-021 — Works on Wi‑Fi not mobile data?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Tunnel/geo — try home Wi‑Fi or VPN to AU. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-022 — 502 on vault URL?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Restart Vaultwarden app on TrueNAS. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-023 — How long is master password?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Long passphrase — copy from handover, don't retype. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-024 — Phone biometric unlock?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. OK after first master login — secure the phone itself. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-025 — Cloudflare login?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Search Cloudflare — needs YubiKey too. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-026 — Car insurance login?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Search insurance — car insurance. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-027 — Mobile bill login?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Search mobile carrier — pay phone bill. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-028 — Amazon Prime login?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Search Amazon — pay Prime. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-029 — Greenfleet login?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Search Greenfleet — pay Greenfleet. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-030 — Password seems wrong?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Check entry history and notes before site reset. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-031 — Deleted item by mistake?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Trash in Bitwarden or restore from export/snapshot. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-032 — Attachments in vault?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Some entries store files — download after unlock. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-033 — Organization / shared vault?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. If Saxon created org — Ryan knows membership. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-034 — Vault on new PC?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Install Bitwarden, set URL, login with master+2FA. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-035 — Emergency access feature?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Check if enabled — Ryan would know Bitwarden org settings. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-036 — Rate limited after tries?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Wait 15–30 min — don't keep guessing. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-037 — LAN access without tunnel?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Ryan may use TrueNAS app port from home network if configured. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-038 — Never put passwords in SaxDocs?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Correct — vault only. FAQs never contain secrets. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-039 — After Saxon died — open vault?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Master password + YubiKey from handover — Ryan helps. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-040 — Wipe vault server?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Never without backup — destroys all passwords. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-041 — Find NPM admin password?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Search NPM or proxy in vault. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden
VLT-042 — More vault help?

Stack context: Vaultwarden @ vault.saxobroko.com Integrated runbooks: Auth stack · Bitwarden

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Open Vaultwarden, Bitwarden doc. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Open Vaultwarden