Getting Started

When FleetMaster launches, it runs a short preflight check sequence before showing the main application. This confirms the workstation can reach the backend services it depends on before you start working.

The Preflight Sequence

The "Getting Started" screen lists each check and updates its status live as it runs:

1. Server Connectivity — confirms the FleetMaster API is reachable.
2. Secure Storage — confirms local secure storage is accessible and reliable.
3. Vault Credential Bootstrap — restores or bootstraps the Vault AppRole credentials required for direct client access to Vault.
4. System Clock Synchronization — verifies the device clock is in sync with the server, to prevent authentication failures caused by clock drift.
5. Vault Connectivity — verifies the HashiCorp Vault server is reachable and responding.
6. FleetMaster Payload Encryption Key — retrieves the tenant's encryption key from Vault.
7. FleetMaster Configuration Warmup — synchronizes any pending configuration (for example, account number) before the main UI opens.

Each row shows a status of Pending, Running…, OK, or Failed. Checks run in order, and a failure on an early check (like Server Connectivity) typically cascades — later checks that depend on the backend being reachable also fail, since Vault bootstrap and configuration warmup both need the server connection to succeed first.

Successful startup

When every check passes, the preflight screen closes automatically and the main FleetMaster window opens.

If a Check Fails

If any check fails, FleetMaster does not continue into the main application. Instead it shows a Startup Error dialog summarizing what went wrong. See Troubleshooting for what to do next, including the most common cause: FleetMaster being unable to reach its (TrikTraks-hosted) server.