Use this when the Chromium extension is installed but the VaultPilot panel remains pending, does not show the device, or pairs once and then stops syncing. Pairing is specific to the account, origin, and browser profile; check all three before recreating packages.
Triage
- Open Browser Extension in VaultPilot and keep the page visible while retrying.
- Confirm the extension server origin exactly matches the VaultPilot host, port and scheme shown to operators.
- Start a new pairing code if the old code expired or if the extension was opened in another browser profile.
- Confirm the extension username matches the signed-in VaultPilot account.
- Unlock at least one vault in the VaultPilot web UI before expecting secret sync.
- Approve the new device from the VaultPilot Browser Extension screen, then revoke stale or duplicated devices.
What to check
| Boundary | Symptom | Action |
|---|---|---|
| Origin | Code accepted but server stays pending | Enter the VaultPilot address exactly, including https and port. |
| Browser profile | Pairing works in one profile but not another | Pair each profile separately or use the intended managed profile only. |
| Account | Device appears under a different user | Sign out of the extension, sign in as the intended VaultPilot user and restart pairing. |
| Vault unlock | Device is approved but no records sync | Unlock the intended vault and verify assigned access. |
| Device list | Multiple rows for the same profile | Revoke stale devices, pair once, and record the new device label. |
Safe evidence
- Extension version and browser family.
- Redacted VaultPilot origin such as
<VAULTPILOT_URL>. - Pairing state: new, pending, approved, revoked or expired.
- Device label and timestamp with user names redacted.
- Console error category only; do not paste tokens or wrapped pairing material.
Security notes
The extension stores PIN-wrapped pairing material in the Chromium profile. Plaintext secret values, master passwords, pairing secrets and API client secrets must not be stored in persistent browser storage, screenshots or support requests.
Related
Still stuck?
Check the troubleshooting guide, then write to support@vaultpilot.io with the version, the steps you took and the exact redacted error. Never attach passwords, vault exports or private keys.