Skip to content

Troubleshooting

Use these tables for first-line diagnosis. Contact Monozu support when the issue involves claim pairing, licensing, or appliance recovery.

SymptomLikely causeWhat to do
Device Offline in Edge DevicesPairing incomplete, firewall, or network outageConfirm Monozu completed claim pairing; check outbound HTTPS to cloud.monozu.io and api.cloud.monozu.ioNetwork & Connectivity
Claim code expiredDelay between on-site registration and pairingAsk Monozu to re-run pairing; technician may need monozu edge register again
Cannot SSH to applianceWrong IP/VLAN or local ACLVerify cabling, DHCP, management VLAN; use local console if available — Connect & Register
Discovery emptyWrong LAN port, module disabled, or scan pendingConfirm LAN cable; wait for scan interval; check license — Asset Discovery
VPN users cannot connectHub hostname, policy, or edge offlineVerify edge Online; review VPN policies
SymptomLikely causeWhat to do
Host stuck in PendingAwaiting administrator approvalApprove Host Agents
Host never appears in PendingWrong enrollment key, expired key, or blocked HTTPSRegenerate key; verify outbound access to api.cloud.monozu.ioInstall
Inventory staleAgent stopped or host offlineCheck service on host; re-approve or reinstall if revoked
Duplicate assetsDiscovery and agent both reported same hostMerge in CMDB; align hostname/MAC conventions
SymptomLikely causeWhat to do
Missing module in navigationLicense not enabledLicense Management
Cannot edit incident / assetRBACPermissions and Groups & Roles
No SLA warning emailsNotification or SLA policy not configuredSLA policies and Notifications
SSO login failsEntra misconfigurationEntra ID SSO
SymptomLikely causeWhat to do
SLA timer not startingNo matching SLA policy for severity/siteCreate or enable policy under Settings → SLA Policies
SLA paused unexpectedlyIncident in waiting state with pause enabledReview incident status and policy pause on waiting option
No breach notificationUser notification preferences offSettings → Notifications — enable incident SLA categories

If browsers or appliances fail only on corporate networks:

  1. Allowlist cloud.monozu.io and api.cloud.monozu.io for outbound HTTPS.
  2. Avoid TLS interception that breaks pinned certificates on edge agents.
  3. Retest from a VLAN that mirrors production egress.

Gather tenant name, site, device or hostname, and approximate time of the issue, then contact Monozu support. For edge pairing, do not share claim codes in unsecured channels.