Nginx 499 timeout and load response

When this happens

Use this when the issue appears during traffic spikes, exports, batch jobs, or slow queries. Do not stop at the screen message; validate latency, worker saturation, connection pools, locks, and long-running jobs first.

Symptom checklist

• 499 appears repeatedly in the Nginx UI or logs.
• server_name, location, proxy_pass, upstream logs differs between successful and failed requests.
• The issue appears only after separating Nginx layer from backend application.
• It often follows deploys, permission changes, configuration edits, or data refreshes.

Likely causes

• 499 specifically changes the investigation surface for Nginx: verify the exact failing object, route, user, and timestamp before applying the broader pattern.
• The client sends a method, content type, header, or body size that the server route does not accept.
• A proxy limit rejects the request before the application handler runs.
• The browser or client aborts while the server is still processing.
• Rate limiting groups unrelated users behind the same IP or token bucket.
• Output is written before headers or redirects are finalized.
• For the timeout and load case, the first useful clue is latency, worker saturation, connection pools, locks, and long-running jobs.

First 1-minute checks

1. Write down the first failure time, latest change, affected user, path, and object ID.
2. Compare server_name, location, proxy_pass, upstream logs for success and failure in the same window.
3. Test the hypothesis: HTTP request rejection caused by method, header, body size, client abort, rate limit, or response-header timing.
4. Classify this as timeout and load: latency, worker saturation, connection pools, locks, and long-running jobs.
5. Capture current values before changing configuration.

First evidence

Treat 499 as a timeout and load case. First collect evidence for latency, worker saturation, connection pools, locks, and long-running jobs.

Output examples

Normal output

Connect, first byte, and total time stay within the expected budget.

Failing output

Connect time, first byte time, or total time spikes before the error.

Output-to-action branches

• The issue appears during traffic spikes, exports, batch jobs, or slow queries.
  Find whether the delay is network connection, upstream processing, database lock, or worker exhaustion.
• The working and failing outputs differ.
  Act on the differing layer first: For 499, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Command output is normal but users still fail.
  Separate browser cache, cookies, permissions, and network location before declaring it fixed.

Do not do this

• Do not only raise timeouts while the synchronous workload remains unchanged.
• Do not change multiple layers before identifying the failing layer.
• Do not delete production data, grant broad permissions, or disable security controls as a first response.

Evidence quality

Auto-generated operator draft: includes issue-specific causes, commands, output branches, and unsafe-action warnings. Official-source links and real incident validation are queued for enrichment.

Commands to run first

grep -R "499" ./logs

nginx -T | grep -n "server_name\|location\|proxy_pass"

tail -n 200 /var/log/nginx/error.log

curl -Iv http://127.0.0.1:3000

ss -lntp

curl -v -X POST https://example.com/path

grep -R "413\|429\|client closed\|headers already" ./logs

nginx -T | grep -n "client_max_body_size\|limit_req"

curl -w 'connect=%{time_connect} start=%{time_starttransfer} total=%{time_total}\n' -o /dev/null -s https://example.com

Fix order

1. Record the full 499 message, failing URL, user, object ID, and latest change.
2. Collect issue-specific evidence for HTTP request rejection caused by method, header, body size, client abort, rate limit, or response-header timing.
3. Compare the failing case with a successful case before editing settings.
4. If this is the timeout and load branch, Find whether the delay is network connection, upstream processing, database lock, or worker exhaustion.
5. Re-check with the same command and URL, then record the normal output.

Actions by cause

• For 499, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Compare the raw failing request with a known-good request.
• Raise body/header limits at every layer only when the route really needs it.
• Separate client aborts from real upstream failures in logs.
• Scope rate limits by user, token, or route instead of a broad IP rule.
• Move redirects, cookies, and headers before any response body output.
• For the timeout and load branch, Find whether the delay is network connection, upstream processing, database lock, or worker exhaustion.

Evidence links

• NGINX Admin Guide official
• NGINX reverse proxy guide official

Verification metadata

• operator-draft
• official-reference-linked
• 2026-07-23

Update queue

• Review cadence
  weekly-source-review
• Next enrichment
  Add one official-source check and one real output example for Nginx 499.

Environment-specific checks

• Shared hosting, proxies, VPNs, or CDN layers can change Nginx layer from backend application results.
• Do not trust only the Nginx UI; compare command output.
• Japanese hosting panels may show completion before DNS or SSL fully propagates.
• Test from both office and external networks.

Prevent it next time

• Store normal examples for server_name, location, proxy_pass, upstream logs.
• Add location priority, proxy headers, and upstream timeout to the release checklist.
• Keep recurring errors in the same note format.
• Split alerts by error rate, latency, certificates, disk, and permission changes.

Related notes

• Nginx 502 Bad Gateway upstream connection failure
• Nginx 301 loop fix note
• Nginx 413 fix note
• Nginx 301 loop fix note 2
• Nginx 413 fix note 2
• Nginx 301 loop fix note 3
• Nginx 413 fix note 3
• Nginx 301 loop fix note 4