THE FIELD GUIDE / FLEET MANAGEMENT
Repair an existing server connection
Pin a trusted fingerprint, rerun the installer and verify a different transport on the same server record.
Verify the host identity
Open the server’s Connection settings and check the saved SSH fingerprint or Unpinned status. Compare a new or rotated key with a fingerprint from the server’s trusted console before saving it. Connection testing directs you to the fingerprint control when trust is missing or mismatched.
Repair or change the connection
Download and rerun the server-specific installer when the existing agent needs recovery. Select the supported connection method, enter its required settings and test the saved route. Complete Finish / verify installation to check the bridge and agent independently.
Keep the original server history
The workflow retains server identity, policies, permissions and historical observations. Diagnose host trust, SSH authentication, bridge reachability and agent verification separately. Role checks, audit records and recovery holds apply throughout.
Open the application reference for capability scope and technical details.
Open View scope in issue #511 ↗