Error Catalog

HTTP errors

Status	Typical meaning	Operator action
400	Bad request or protocol issue.	Check protocol hardening logs and client request format.
403	Blocked by L4, GEO, WAF, route, or policy.	Inspect rule_id, module, and reason.
404	No matching route or backend path.	Check routes and upstream application path.
429	Rate limit exceeded.	Inspect rate-limit rule and client key.
502	Backend connection failed.	Check backend health, DNS, TLS, and firewall.
503	No healthy backend or service unavailable.	Check backend pool and health path.
500	Internal service error.	Check component logs and recent config changes.

Operational errors

Error	Cause	Resolution
Core disconnected	Managerd cannot reach Core IPC.	Start Core and check socket path/permissions.
mTLS handshake failed	CA/cert/key mismatch or SAN issue.	Verify mTLS files and hostname.
License validation failed	Portal unreachable, token invalid, expired, or revoked.	Check portal connectivity and entitlement.
Backend unhealthy	Health path failing or TLS verification failing.	Test backend directly from Core host.
Config parse failed	Invalid keyword or syntax.	Revert to last known-good config and validate syntax.
High Managerd CPU	Excessive polling or live event streams.	Reduce polling, use backoff, close live views.
Logs filling disk	Retention too long or high traffic.	Reduce retention, forward logs, increase disk.