Incident console · Case 0

Store unavailable

Preparing LOW
Incoming incident · Case 0 · 10:00 · your first day on call

After an update, customers cannot open the store: the page returns 502 Bad Gateway. The server is reachable and nginx is running, but shop-api does not respond. Find the cause and restore the store, from your first check to a successful customer request.

Symptoms

  • The store homepage at http://localhost returns 502 Bad Gateway
  • The server is reachable and nginx is running, but it gets no response from shop-api
  • The application check at http://localhost:8080/health does not return a successful response

Recent changes

  • A developer has just updated shop-api
  • After the deployment, customers reported that the store would not open

Your task

  1. Check the state of shop-api and find out why nginx gets no response from it
  2. Resolve the cause of the application outage and restore the store
  3. Verify that the store and its health check respond successfully; a running process alone is not enough
Prepare the practice when you are ready.

Restore the store at your own pace.

Prepare for this caseLearn ↗

Explore the relevant skills before practice. Lessons open in a new tab.

All preparation for this case →

Incident resolved · Case 0

Store unavailable

The store is taking orders again. Your first incident is resolved!

Next case →