Troubleshooting
Common issues and what they actually mean.
The connection test fails
- Check address, port and user, then confirm you can reach the server with a regular SSH client from the same PC.
- Firewalls and VPNs: the app connects from your PC, so your PC's network path must allow SSH to the server.
- Key-based auth: confirm the key path is still valid and the passphrase is correct.
“Host key mismatch” blocks the connection
This is the security model working. If the change is expected (reinstall or key rotation), remove the stored trust for the server and approve the new fingerprint. If it is not expected, investigate before trusting.
Metrics show a dash
A dash means “couldn't read this value”, never zero. It usually indicates a command failing on that server, permissions, an unusual distribution, or a transient error. The next successful refresh fills it in.
Docker section says not available
Docker isn't installed, the daemon isn't running, or your SSH user lacks permission to query it. ServerAlyzer reports the state it found; granting the SSH user Docker access (on the server) is your call.
No discovery suggestions appear
Start a discovery search to query SSH services announced through mDNS on the local network. If no results appear, check the server announcement and firewall permissions. Add machines on other subnets or without mDNS manually.
History has gaps
Gaps are recorded honestly whenever samples couldn't be collected, server unreachable, PC asleep or app closed. They are information, not an error.
