Cloudflare 1020 local versus production drift response

When this happens

Use this when it works locally but fails only on the deployed server. Do not stop at the screen message; validate runtime version, environment variables, file paths, locale, timezone, and permissions first.

Symptom checklist

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

• 1020 specifically changes the investigation surface for Cloudflare: verify the exact failing object, route, user, and timestamp before applying the broader pattern.
• A firewall rule blocks the path, country, ASN, IP, or user agent.
• A managed WAF rule matches a payload that the app expects.
• Bot protection challenges API or logged-in traffic.
• Rule order applies a broad block before a later allow rule.
• The app sees no request because Cloudflare blocks it at the edge.
• For the local versus production drift case, the first useful clue is runtime version, environment variables, file paths, locale, timezone, and permissions.

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 WAF or firewall block caused by rule order, bot score, country/IP rule, or managed ruleset match.
4. Classify this as local versus production drift: runtime version, environment variables, file paths, locale, timezone, and permissions.
5. Capture current values before changing configuration.

First evidence

Treat 1020 as a local versus production drift case. First collect evidence for runtime version, environment variables, file paths, locale, timezone, and permissions.

Output examples

Normal output

Runtime, env values, paths, and permissions match the documented production baseline.

Failing output

Production uses a different version, env var, path, locale, timezone, or user.

Output-to-action branches

• It works locally but fails only on the deployed server.
  Print effective runtime state from the failing process, not only from the login shell.
• The working and failing outputs differ.
  Act on the differing layer first: For 1020, 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 trust CLI output if the web worker, service, or container runs as another user.
• 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 "1020" ./logs

grep -R "1020\|firewall\|waf" ./logs

curl -I https://example.com/protected-path

curl -A 'known-client' -I https://example.com/protected-path

echo 'Check Cloudflare Security Events by Ray ID and ruleset ID'

printenv | sort && pwd && id

Fix order

1. Record the full 1020 message, failing URL, user, object ID, and latest change.
2. Collect issue-specific evidence for Cloudflare WAF or firewall block caused by rule order, bot score, country/IP rule, or managed ruleset match.
3. Compare the failing case with a successful case before editing settings.
4. If this is the local versus production drift branch, Print effective runtime state from the failing process, not only from the login shell.
5. Re-check with the same command and URL, then record the normal output.

Actions by cause

• For 1020, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Review Cloudflare security events for the exact rule ID.
• Narrow the block rule or add a scoped skip rule for the affected path.
• Separate browser traffic from API traffic before changing bot settings.
• Move allow rules above broad blocks when appropriate.
• Keep the Ray ID and matched ruleset in the runbook.
• For the local versus production drift branch, Print effective runtime state from the failing process, not only from the login shell.

Evidence links

• 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 1020.

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