Troubleshooting
Common issues connecting machines and reading topology, and how to fix them.
Machine shows offline
- Check the service is running:
sudo systemctl status ic-agent journalctl -u ic-agent -n 50 --no-pager - Confirm outbound HTTPS/WSS to
cloud.infracanvas.appis allowed. - Verify the API key in the unit is valid (rotated keys stop working).
Kubernetes (or Docker) resources missing
Usually a scope or permissions problem:
- The agent's scope must include
kubernetes/docker. See scopes. - The agent must run as a user that can reach them. If installed via
curl | sudo bashas root, root needs a kubeconfig (KUBECONFIG) and Docker access — otherwise those scopes go dark. The installer normally runs the agent as your login user to avoid this.
Adding a second account disconnected the first
The agent must be 1.4.0 or newer for multi-account. Update it from the machine card, then re-run the connect command with the new key. See connecting multiple accounts.
Action output looks empty or wrong
Make sure the agent is up to date — older agents had gaps in some host actions. Update from the machine card.
Metrics aren't showing
- Metrics history requires a paid plan (Starter and up). See metrics.
- Trends accumulate from the time you upgrade — there's no retroactive history.
Still stuck?
Email support or reach out from the dashboard.