Nginx Server Errors

Service Unavailable

503
HighWeb Server

Reviewed for reference consistency: August 11, 2026

Nginx temporarily refuses the request through rate, connection, or maintenance limits

What 503 Means

The 503 error on the Nginx Server Errors indicates service unavailable — nginx temporarily refuses the request through rate, connection, or maintenance limits. This typically occurs due to nginx worker connection limits reached.

A 503 from Nginx means the request arrived but the server deliberately had nothing to serve it with at that moment — a rate or connection limit triggered, or a maintenance state is holding the location. Unlike a 500, the code names a known state: the server is up and expects to serve again.

Technical Background

Unlike a 502 Bad Gateway where Nginx tries to connect and fails, a 503 means Nginx knows it shouldn't even attempt to serve the request right now.

The code marks a temporary capacity condition rather than a broken software path.

Common Causes

  • Nginx worker connection limits reached
  • Upstream server is temporarily down for maintenance
  • Rate limiting exceeded the configured `limit_req` zone threshold

Typical Scenarios

  • A massive surge of traffic maxes out the `worker_connections` setting.
  • The `limit_req` directive enforces its rate cap during a request flood.
  • An upstream proxy is manually marked as 'down' in the upstream block.

What to Know

Monitoring Nginx worker limits and reviewing `limit_req` zones are the primary operational responses during sustained traffic spikes.

Frequently Asked Questions

Common questions about Nginx 503 error

A 502 means Nginx tried to reach the backend app and it crashed. A 503 means Nginx is intentionally refusing traffic due to overload or maintenance.

Related Error Codes

Related Errors From Other Categories

Similar error codes documented across different platforms and systems