Use this article when screens such as Audit Log, Passwords, Updates, Users or Browser Extension show access errors or empty data right after login.
Expected behavior in VaultPilot 3.0.3
VaultPilot confirms the new session with the server before it treats the vault as unlocked, and the session survives page refreshes until it times out. Workspace screens load only after that confirmation. If the session cannot be confirmed, the screen locks and clears cached data instead of retrying again and again.
First checks
| Check | Healthy result |
|---|---|
| Installed version | The console reports VaultPilot 3.0.3 or newer. Move older deployments to the current official release before contacting support. |
| Login | Sign-in completes without an error message. |
| Session | The workspace opens unlocked after sign-in and stays unlocked after a refresh. |
| Workspace screens | Audit, passwords, browser extension, updates, users and integrations load their data. |
| Browser mode | Cookies are not blocked for the VaultPilot host. |
| Address consistency | Login and workspace use the same host, https and port. |
Common causes
- The browser blocks or clears the session cookie.
- The operator signs in through one host name but continues through another host name or IP.
- A service restart ended the current session.
- An old tab keeps refreshing screens after the user was locked.
- A reverse proxy changes the cookie, host or
httpshandling.
Safe evidence to collect
- VaultPilot version, plus the legacy PassMan version only for upgraded installs.
- Host name replaced by
<SERVER_HOST>. - Whether the workspace stays unlocked after sign-in.
- Which screens fail and the error message they show.
- Browser family and whether cookies are blocked.
- Whether the issue appears after refresh, service restart, update or host change.
Do not send master passwords, cookies, session token values, screenshots with real records or raw logs with secret values.
Resolution path
- Install or upgrade to the official VaultPilot 3.0.3 release or newer.
- Sign out, close old tabs and open VaultPilot from one address.
- Confirm browser cookies are allowed for the VaultPilot host.
- Sign in again and check whether the workspace stays unlocked before opening other screens.
- If a proxy is used, confirm it keeps the host,
httpsand cookies unchanged. - If the issue continues, email the safe evidence pack to support@vaultpilot.io.
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.