Access required
Site returns 502 Bad Gateway
What the on-call engineer sees
- The store returns 502 Bad Gateway
- Monitoring: almost all nginx responses are 5xx errors
- nginx is running and accepting connections
You need an account to take this incident. Registration is free and takes a minute: just a username and password, with no email or phone number. The case you completed as a guest will carry over.
Without an account, you can complete case 0, “Store unavailable” —a short introduction in a real console.
Prepare for this caseLearn ↗
Explore the relevant skills before practice. Lessons open in a new tab.
- Load balancing: replicas and health checks14 min ↗
- Ports and upstreams: where requests go12 min ↗
- The request path: name, route, port, application12 min ↗