FixOps
Play now
Docker Intermediate About 25 min +180 XP

Web Container Is Unreachable on Port 80

Browser customers get connection refused on port 80 while the storefront's web container reports Up.

Take this incident no signup All incidents

Stage 2 of 4 in Platform Recovery Ladder.

Briefing

The frontend team redeployed the storefront's web container about thirty minutes ago, and every request to port 80 has been refused at connect time ever since.

Compose reports the container Up for the whole period, and nginx inside it has logged nothing alarming.

The team's own smoke test after the deploy passed, which is why customers noticed before anyone on the team did.

Sam's first guess is a host firewall rule from the same change window.

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.

All 61 incidents
Docker Beginner

Web Container Exits After Startup

The launch API's container exits with status 0 a moment after every start, so nothing is serving.

+140 XP20 minStage 1/4

Docker Intermediate

Database Rows Vanish After Restart

Each time the postgres container is recreated, the orders database comes back empty and earlier rows are gone.

+200 XP30 minStage 3/4

Kubernetes Intermediate

API Pods Restart Across the Rollout

Every api replica is in CrashLoopBackOff and the Deployment has shown 0 of 3 available for ten minutes.

+220 XP35 minStage 4/4

Your pager is ready.

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

Take this incident no signup Get it on Google Play