Web Intermediate About 30 min +220 XP

Order API Returns 502 Through Nginx

Every order API request through the edge returns 502 Bad Gateway, so checkout cannot submit orders.

Briefing

Checkout started failing just after the overnight maintenance window, and every request to /api/ on the edge now comes back as nginx's 502 page.

The edge itself is up, and its proxy configuration has not changed in weeks.

The first message in the channel blames the nginx package update that went out in the same window.

The orders team is asleep, so whoever takes this page owns both tiers until morning.

The fix is yours to find: hints, the recovery checks and the debrief unlock inside the incident.

How it plays

  1. 01

    Get paged

    The alert fires and the clock starts. Read the page and the briefing.

  2. 02

    Investigate

    Work in a simulated shell with realistic output: logs, configs, services.

  3. 03

    Fix it

    Change the system the way you would in production. Hints are there if you get stuck.

  4. 04

    Prove it

    Automated checks verify the recovery, then the debrief explains what happened.

Your pager is ready.

Free, instant, and it works on your phone. No signup: start as a guest and save your progress later.