Skip to content
CasesNew Learn 30 Career · co-op History Leaderboard Log in
EN
English✓ Русский

Access required

HIGH Case 8 · 20 min

Site returns 502 Bad Gateway

After an application release, nginx returns 502 to customers even though nginx itself is running.

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.

Sign up Log in

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 ↗
All preparation for this case →
Site terms · Privacy policy · Cookie settings · privacy.prodisdown@yandex.ru · Find us on VK · Find us on TikTok

We use cookies and Yandex Metrica to analyze visits. Learning analytics for signed-in users are linked to their account. By selecting “Accept”, you agree to the terms of data processing.