Japan Server Error Fix Lab

Home / Cloudflare / Cloudflare

Cloudflare 522 first triage response

A Cloudflare first triage note for 522: Cloudflare timeout caused by blocked TCP connection, slow origin response, firewall filtering, or overloaded upstream. It includes evidence, output examples, branches, and the smallest reliable fix.

low5227 min read
First command
grep -R "522" ./logs
First evidence

Treat 522 as a first triage case. First collect evidence for the first observable mismatch before any setting is changed.

Search queries
Cloudflare 522Cloudflare error 522Cloudflare 522 first triage response

When this happens

Use this when only the visible message is known. Do not stop at the screen message; validate the first observable mismatch before any setting is changed first.

Symptom checklist

  • 522 appears repeatedly in the Cloudflare UI or logs.
  • CF-Ray, SSL mode, proxied DNS, origin response differs between successful and failed requests.
  • The issue appears only after separating proxied requests from direct origin requests.
  • It often follows deploys, permission changes, configuration edits, or data refreshes.

Likely causes

  • 522 specifically changes the investigation surface for Cloudflare: verify the exact failing object, route, user, and timestamp before applying the broader pattern.
  • The origin does not complete TCP connection from Cloudflare IP ranges.
  • A firewall or hosting panel blocks Cloudflare edge addresses.
  • The upstream app accepts the request but cannot respond before the timeout.
  • Keepalive, worker, or database saturation makes only some requests hang.
  • Large exports or slow reports exceed the proxy timeout window.
  • For the first triage case, the first useful clue is the first observable mismatch before any setting is changed.

First 1-minute checks

  1. Write down the first failure time, latest change, affected user, path, and object ID.
  2. Compare CF-Ray, SSL mode, proxied DNS, origin response for success and failure in the same window.
  3. Test the hypothesis: Cloudflare timeout caused by blocked TCP connection, slow origin response, firewall filtering, or overloaded upstream.
  4. Classify this as first triage: the first observable mismatch before any setting is changed.
  5. Capture current values before changing configuration.

First evidence

Treat 522 as a first triage case. First collect evidence for the first observable mismatch before any setting is changed.

Output examples

Normal output

No matching error appears during the affected request window.

Failing output

The same error appears at the exact request time with the affected path, user, or object.

Output-to-action branches

  • Only the visible message is known.
    Collect timestamp, route, request ID, user, and the first backend log line before editing configuration.
  • The working and failing outputs differ.
    Act on the differing layer first: For 522, 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 change DNS, SSL, cache, and permissions at the same time.
  • 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 "522" ./logs
nc -vz ORIGIN_IP 443
mtr -rw ORIGIN_IP
curl --connect-timeout 5 -Iv https://example.com --resolve example.com:443:ORIGIN_IP
grep -R "522\|524\|upstream timed out" ./logs /var/log/nginx
date -u && grep -R "ERROR\|WARN\|failed" ./logs | tail -n 50

Fix order

  1. Record the full 522 message, failing URL, user, object ID, and latest change.
  2. Collect issue-specific evidence for Cloudflare timeout caused by blocked TCP connection, slow origin response, firewall filtering, or overloaded upstream.
  3. Compare the failing case with a successful case before editing settings.
  4. If this is the first triage branch, Collect timestamp, route, request ID, user, and the first backend log line before editing configuration.
  5. Re-check with the same command and URL, then record the normal output.

Actions by cause

  • For 522, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
  • Test origin port reachability and allow Cloudflare IP ranges.
  • Measure direct origin response time before touching DNS.
  • Move long-running jobs out of the request path.
  • Tune upstream worker, database, or queue saturation.
  • Return an early accepted response for slow background work.
  • For the first triage branch, Collect timestamp, route, request ID, user, and the first backend log line before editing configuration.

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 Cloudflare 522.

Environment-specific checks

  • Shared hosting, proxies, VPNs, or CDN layers can change proxied requests from direct origin requests results.
  • Do not trust only the Cloudflare 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 CF-Ray, SSL mode, proxied DNS, origin response.
  • Add SSL mode, origin certificate, and Cloudflare IP allow rules to the release checklist.
  • Keep recurring errors in the same note format.
  • Split alerts by error rate, latency, certificates, disk, and permission changes.