AFW-513 — Collector offline

Area: Cloud sync · All support codes · Reference table

Why this happened

The collector has stopped heartbeating, so the cloud has no current view of it. It keeps enforcing its last-synced policy while it's away; the console simply can't see it.

Fix

Check the collector host is up and the service is running (systemctl status kilasec-collector), then its own log for why it stopped. If the host is fine, this is usually outbound HTTPS to the cloud being blocked.

---

If the fix doesn't resolve it, file a support ticket from the console — your workspace's diagnostics snapshot is attached automatically, so this code reaches support with its context.