Troubleshooting

Machine shows offline

1. Check the service is running:

   sudo systemctl status ic-agent
   journalctl -u ic-agent -n 50 --no-pager

2. Confirm outbound HTTPS/WSS to cloud.infracanvas.app is allowed.
3. 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 bash as 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.

Cluster won't connect (direct connect)

Almost always an auth problem, not a networking one:

• exec: auth kubeconfigs don't work with direct connect. If your kubeconfig came from aws eks update-kubeconfig, gcloud container clusters get-credentials, or az aks get-credentials, it authenticates by executing the aws / gcloud / az CLI — which runs on InfraCanvas's backend, not your machine, and isn't configured there. Use the relay pod option instead; see Clusters for why.
• API server not reachable from the internet. Direct connect needs InfraCanvas's backend to reach your cluster's API server. Private/VPC-only clusters need the relay pod instead.
• Wrong context selected. A kubeconfig with several contexts requires picking the right one at connect time — reconnect and double-check you picked the intended cluster.

Cluster won't connect (relay pod)

1. Check the pod is actually running: kubectl get pods -n infracanvas
2. Check its logs: kubectl logs -n infracanvas deploy/infracanvas-relay-agent
3. Confirm the cluster has outbound HTTPS/WSS access to cloud.infracanvas.app — the pod connects outbound only, same as a VM agent, so no inbound rule is needed, but egress must be allowed.

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 are collected from the moment an agent connects; there's no retroactive history. See metrics.
• If a machine was recently added, give it a few minutes to report its first data points.

Still stuck?

Email support or reach out from the dashboard.