Common Issues
Dashboard sign-in fails
Section titled “Dashboard sign-in fails”Check:
AUTH_OKTA_ID,AUTH_OKTA_SECRET,AUTH_OKTA_ISSUERAUTH_SECRET- Okta callback URL matches
/api/auth/callback/okta
Dashboard loads but server data is empty
Section titled “Dashboard loads but server data is empty”Check:
NEXT_PUBLIC_CONVEX_URLis set and reachable- Convex deployment has server records
- User session is authenticated
Server shows offline/unavailable
Section titled “Server shows offline/unavailable”From dashboard host (or reachable network segment):
curl https://<server>:<port>/api/healthUse the configured scheme/port from your [api] config or reverse-proxy/TLS settings.
If unreachable:
- Confirm firewall rules
- Confirm
license-monitoris running - Confirm bind settings in
[api](these still apply to the upstream service when using a proxy/TLS front end)
No license data in dashboard
Section titled “No license data in dashboard”On monitored host, test monitor command locally:
license-monitor --test --execute "lmstat -a"Then verify API output:
Use the configured scheme/port from your [api] config or reverse-proxy/TLS settings:
curl <scheme>://<host>:<port>/api/licenses?refresh=trueConvex scheduled checks fail for private servers
Section titled “Convex scheduled checks fail for private servers”Convex-hosted jobs must be able to reach monitored hosts. For private-only hosts, use a reachable proxy path or private-network-compatible architecture.