Use this if VaultPilot Server System settings were saved but browser access, HTTPS, notifications, logs, or service restart state still need review.
Start with these checks
| Check | Healthy result |
|---|---|
| Access address | Operators use one https://<SERVER_HOST>:<PORT> address. |
| Service state | VaultPilotServer is running; upgraded hosts may also show the legacy PassManServer name. |
| HTTPS state | The certificate subject or SAN matches the host users open in the browser. |
| Notification test | The test mail succeeds or shows a mail-server error without secrets. |
| Maintenance state | Retention values are visible; cleanup is Owner-only, takes a backup first, and is not needed for normal operation. |
Common causes
- Host or port changed, but DNS, firewall or bookmarks still point to the old address.
- The certificate package was saved, but users open a host name that is not in the SAN.
- SMTP credentials or relay policy changed outside VaultPilot.
- A configuration change needs the service restart the screen asked for.
- An operator expects maintenance to purge broad data, but cleanup covers only Audit, Discovery or Executions records and always takes a backup first.
Maintenance cleanup boundary
Maintenance cleanup is Owner-only. It is not routine troubleshooting; use it only when support or a retention decision calls for it.
VaultPilot clears a category only after writing a maintenance backup file of that category; a clear without the backup option is refused.
Restore affects only the category in that backup. Records created after the backup may change or be lost during restore, and the screen warns about this first. Cleanup and restore never touch vault secrets, source files, service logs, databases, backup files, certificates or customer data.
Safe evidence to collect
- VaultPilot version and installed service name.
- Host name replaced by
<SERVER_HOST>. - Configured port and whether the service was restarted after saving.
- Certificate subject or SAN summary and expiry date.
- Notification test time and the error message without secrets.
- Log retention and audit retention values.
- Cleanup category and maintenance backup file name, if cleanup was explicitly approved.
Do not send certificate files, private keys, certificate passwords, SMTP secrets, cookies, API tokens, raw logs that may contain secrets, databases, backups or maintenance backup files.
Resolution path
- Reopen VaultPilot from one address.
- Confirm the Windows service is running.
- Confirm DNS and firewall lead to the configured host and port.
- If HTTPS was changed, restart only when the screen asks, then test from a client browser.
- If the notification test fails, confirm relay host, port, TLS mode and sender policy with the mail administrator.
- If maintenance cleanup was explicitly approved, confirm the category is Audit, Discovery or Executions, keep the backup option on, and store the maintenance backup privately.
- 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.