Support codes

Every customer-facing Kilasec failure carries a stable AFW-### code, and every code has its own page here with the cause and the fix — the same text the console shows on a code chip. AI tools can read the whole registry as JSON, no auth, at https://kilasec.com/api/support/codes.

Prefer one table? See the error-code reference.

1xx — Install & collector boot

• AFW-111 — Data plane not listening
• AFW-112 — Collector port already in use
• AFW-113 — Device port 443 not available
• AFW-120 — Collector CA problem
• AFW-130 — Collector update reverted
• AFW-131 — Collector restart loop
• AFW-140 — File-descriptor limit too low
• AFW-141 — Low disk space

2xx — Enforcement & data plane

• AFW-210 — Policy sync refused
• AFW-211 — Policy tamper detected
• AFW-220 — Collector degraded (pass-through)
• AFW-221 — Fail-open episode
• AFW-222 — Fail-closed episode
• AFW-223 — Collector overloaded (shedding)
• AFW-230 — Events dropped
• AFW-231 — Content not fully scanned

3xx — Identity & connectors

• AFW-310 — User-ID: WinRM authentication failed
• AFW-311 — User-ID: access denied reading the Security log
• AFW-312 — User-ID: cannot reach WinRM on the DC
• AFW-313 — User-ID: WinRM TLS failed
• AFW-320 — Directory sync: bind failed
• AFW-321 — Directory sync: server unreachable
• AFW-322 — Directory sync: base DN not found
• AFW-323 — Directory sync: TLS failed

4xx — Licensing

• AFW-410 — Subscription lapsed
• AFW-411 — Subscription suspended
• AFW-420 — Collector limit reached
• AFW-421 — Device limit reached

5xx — Cloud sync

• AFW-510 — Collector-to-cloud sync failing
• AFW-511 — Collector token rejected
• AFW-512 — Collector clock skew

6xx — Device client

• AFW-610 — Collector refused the device token