Troubleshooting
Startup Error: Can't Reach the FleetMaster Server
Symptom: FleetMaster's preflight sequence fails almost immediately. Server Connectivity shows Failed with a message like:
Could not connect to http://127.0.0.1:5090/api/v1/fleetmaster/health/ping after 3
attempts.
Because every later check needs that same backend connection, the failure cascades: Vault Credential Bootstrap, System Clock Synchronization, Vault Connectivity, and FleetMaster Payload Encryption Key all fail in turn (only Secure Storage, which is purely local, and FleetMaster Configuration Warmup — which has nothing to synchronize when there's no account data — succeed).
FleetMaster then shows a Startup Error dialog instead of opening the main application:
| Field | Value |
|---|---|
| Detected Issue | Vault configuration is missing or invalid. |
| Resolution | Set required Vault settings (Address, BasePath, and auth fields) before startup, then retry. |
| Error Code | FM-STARTUP-0009 |
The dialog's stated "Detected Issue" (Vault configuration) reflects the deepest check in the chain that couldn't complete — not necessarily the root cause. When Server Connectivity fails first, treat every check below it as a symptom of the same root problem, not a separate issue to fix individually.
Resolution: The FleetMaster server is hosted by TrikTraks — it isn't something you run or restart yourself. If you see this error:
- Check your own internet connectivity first. Confirm your workstation can reach the internet normally (try loading another site), and that no firewall or VPN is blocking the connection.
- If your connection is fine, contact support. This points to a problem on our
side. Support is available to all paying customers — include
the Error Code (
FM-STARTUP-0009, copyable from the dialog) so we can look into it right away.
The Diagnostic Log field on the error dialog points to a local log file with the full technical detail — attaching it speeds up resolution but isn't required to open a support request.
Still stuck?
If you're unsure whether an issue is on your end or ours, don't spend time troubleshooting further — open a support request with the Error Code shown on the dialog. Support can confirm server status and follow up once it's resolved.