503
503.my.id
THE 503 ERROR DIAGNOSTIC CENTER
503

The symptom

A request knocks. Nginx sends back 503.

The default page names no culprit — Nginx knows three different doors that produce this exact answer.

GET / HTTP/1.1 HTTP/1.1 503 Service Temporarily Unavailable

Three doors

Limits, rules, or the upstream — one of them fired.

LIMIT
limit_req · limit_conn
RULE
return 503
UPSTREAM
PHP-FPM · app

Each door leaves a different fingerprint. Guessing wastes the outage; the log knows which one.

The evidence

Three log fingerprints, three different doors.

ERROR LOG — LIMIT

limiting requests, excess: 3.000 by zone "lab8_burst"

PHP-FPM LOG — UPSTREAM

server reached pm.max_children setting (3)

RULE — THE SILENT ONE

no new error line — the header confesses: Retry-After: 3600

200 OK

One fix, door by door

Our lab fix: open the LIMIT door wider.

rate=1r/m · burst=2 rate=20r/s · burst=20

200 OK — 10 of 10 requests passed in our lab retest

Every door has its own fix — the log line from scene three names yours.

Nginx 503 Service Temporarily Unavailable: Fix Guide by 503.my.id.