Cloudflare 520 rollback or roll-forward response

When this happens

Use this when the fix choice is between rollback, hotfix, config revert, or data repair. Do not stop at the screen message; validate the smallest reversible change that restores service without hiding data corruption first.

Symptom checklist

• 520 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

• 520 specifically changes the investigation surface for Cloudflare: verify the exact failing object, route, user, and timestamp before applying the broader pattern.
• The origin returns malformed or oversized headers that Cloudflare cannot proxy.
• The origin server intermittently crashes or closes the connection.
• Cloudflare points to an origin IP that no longer serves the requested host.
• A reverse proxy in front of the app returns a different result than the app itself.
• The visible Cloudflare code hides a lower-level origin log error.
• For the rollback or roll-forward case, the first useful clue is the smallest reversible change that restores service without hiding data corruption.

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 origin response failure caused by malformed origin headers, origin crash, DNS-to-origin mismatch, or proxy/origin disagreement.
4. Classify this as rollback or roll-forward: the smallest reversible change that restores service without hiding data corruption.
5. Capture current values before changing configuration.

First evidence

Treat 520 as a rollback or roll-forward case. First collect evidence for the smallest reversible change that restores service without hiding data corruption.

Output examples

Normal output

A rollback plan exists and the previous version is compatible with current data.

Failing output

The current version changed schema, cache, or external state that a simple rollback cannot reverse.

Output-to-action branches

• The fix choice is between rollback, hotfix, config revert, or data repair.
  Check reversibility first, then choose the smallest action with clear verification.
• The working and failing outputs differ.
  Act on the differing layer first: For 520, 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 rollback schema-affecting releases without checking migration direction.
• 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 "520" ./logs

curl -Iv https://example.com --resolve example.com:443:ORIGIN_IP

curl -sI https://example.com | grep -i 'cf-ray\|server'

grep -R "520\|521\|523\|530" /var/log/nginx /var/log/apache2 ./logs

dig +short example.com

git show --stat --oneline HEAD && git status --short

Fix order

1. Record the full 520 message, failing URL, user, object ID, and latest change.
2. Collect issue-specific evidence for Cloudflare origin response failure caused by malformed origin headers, origin crash, DNS-to-origin mismatch, or proxy/origin disagreement.
3. Compare the failing case with a successful case before editing settings.
4. If this is the rollback or roll-forward branch, Check reversibility first, then choose the smallest action with clear verification.
5. Re-check with the same command and URL, then record the normal output.

Actions by cause

• For 520, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Compare Cloudflare-routed requests with direct origin requests using --resolve.
• Inspect CF-Ray and origin logs for the same timestamp.
• Fix malformed headers, crashed workers, or virtual host routing at the origin.
• Confirm DNS records point to the intended origin IP.
• Keep the failing CF-Ray value with the incident note.
• For the rollback or roll-forward branch, Check reversibility first, then choose the smallest action with clear verification.

Evidence links

• Cloudflare error 520 official
• Cloudflare 5xx errors official
• Cloudflare status code analytics 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 Cloudflare 520.

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.

Related notes

• Cloudflare SSL 525 handshake failed
• Cloudflare 520 fix note
• Cloudflare 521 fix note
• Cloudflare 522 fix note
• Cloudflare 524 fix note
• Cloudflare 520 fix note 2
• Cloudflare 521 fix note 2
• Cloudflare 522 fix note 2