Skip to main content

502/503 from nginx

Common message

502 Bad Gateway|503 Service Temporarily Unavailable

Symptoms​

  • Visiting the OpenClaw URL returns 502/503 from nginx
  • Deployment popup may claim success but URL is not ready

Root cause​

Ingress routes to a service with no ready pods (image pull backoff, init container failing, crash loop).

Fix​

  1. Check pod readiness and recent events inside the tenant vCluster namespace.
  2. Remove failing init containers when the feature is not used (skill-pack init should be conditional).
  3. Confirm the service selector matches pod labels.