Skip to content

Diagnostics

Marc Pope edited this page Oct 8, 2026 · 3 revisions

Fleet diagnostics

Since 1.7.0.

System → Diagnostics: one page that answers "is everything up?" — the application, database, ID server and relay reachability, local API, WebSocket readiness, scheduler heartbeat, the ID server link and SMTP state, plus fleet counts and the client version spread.

ID server link (since 1.10.0) shows when hbbs last fetched the server access policy. A stale Scheduler card on a manual install, with cron running, is the lock problem fixed in 1.10.1; see Troubleshooting.

Fleet diagnostics page with status cards for application, database, ID server, relay, API, WebSocket bridge, scheduler and SMTP

Server probes are TCP with a one-second timeout. SMTP stays Unknown until a real send has been observed — the page never sends test email on its own. Version status compares against the newest client in your own fleet, not a vendor feed.

Sanitized JSON exports the report with hosts, IPs, URLs, keys and device identities stripped, so it can be pasted into a bug report as-is.

This is a status page, not monitoring: it reports when you open it. For alerts that come to you, see Notifications. For load balancers and uptime monitors, see Health checks.

Related

Clone this wiki locally