Cloudflare / Cloudflare

Cloudflare Error 520 vs 522 vs 524 — Origin Server Returns Garbled Response After Connection Succeeds

Diagnose and fix Cloudflare 520 error when origin server returns garbled or empty response after TCP connection succeeds, distinguishing from 522 timeout and 524 gateway timeout Includes evidence for Cloudflare troubleshooting demand.

Source-backed Last updated June 2, 2026 3 sources Needs local verification

Category: Cloudflare
Error signature: "Error 520: web server returns an unknown error" — connection established but response is empty/malformed/reset
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: June 2, 2026
Verification status: Source-backed
Evidence: 3 public source URLs

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Cloudflare, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

"Error 520: web server returns an unknown error" — connection established but response is empty/malformed/reset is a Cloudflare failure pattern reported for developers trying to diagnose and fix cloudflare 520 error when origin server returns garbled or empty response after tcp connection succeeds, distinguishing from 522 timeout and 524 gateway timeout. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Critical infrastructure error affecting production sites globally. 520 is distinct from 522 (connection timeout before response) and 524 (gateway timeout after 100s wait). Common causes: server crashes/resource exhaustion, oversized response headers (>128KB), HTTP/2 misconfiguration, firewall blocking Cloudflare IPs. Official Cloudflare docs + independent analysis both provide detailed troubleshooting. High search demand given it's a common production outage symptom.

Common causes

Critical infrastructure error affecting production sites globally. 520 is distinct from 522 (connection timeout before response) and 524 (gateway timeout after 100s wait). Common causes: server crashes/resource exhaustion, oversized response headers (>128KB), HTTP/2 misconfiguration, firewall blocking Cloudflare IPs. Official Cloudflare docs + independent analysis both provide detailed troubleshooting. High search demand given it's a common production outage symptom.

Quick fixes

Confirm the exact error signature matches "Error 520: web server returns an unknown error" — connection established but response is empty/malformed/reset.
Check the Cloudflare account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match "Error 520: web server returns an unknown error" — connection established but response is empty/malformed/reset exactly before applying the quick fix.
Compare the failing environment with Cloudflare versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does "Error 520: web server returns an unknown error" — connection established but response is empty/malformed/reset mean in Cloudflare?

"Error 520: web server returns an unknown error" — connection established but response is empty/malformed/reset indicates the workflow described by "Cloudflare Error 520 vs 522 vs 524 — Origin Server Returns Garbled Response After Connection Succeeds" failed in a Cloudflare context. Start by confirming the exact signature and the component that emitted it.

What should I check first for "Error 520: web server returns an unknown error" — connection established but response is empty/malformed/reset?

Check whether this cause matches your environment: Critical infrastructure error affecting production sites globally. 520 is distinct from 522 (connection timeout before response) and 524 (gateway timeout after 100s wait). Common causes: server crashes/resource exhaustion, oversized response headers (>128KB), HTTP/2 misconfiguration, firewall blocking Cloudflare IPs. Official Cloudflare docs + independent analysis both provide detailed troubleshooting. High search demand given it's a common production outage symptom.

Is the "Error 520: web server returns an unknown error" — connection established but response is empty/malformed/reset guidance source-backed?

The "Cloudflare Error 520 vs 522 vs 524 — Origin Server Returns Garbled Response After Connection Succeeds" page is labeled source-backed. It has 3 public source URLs from contabo.com, developers.cloudflare.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for "Error 520: web server returns an unknown error" — connection established but response is empty/malformed/reset?

For "Cloudflare Error 520 vs 522 vs 524 — Origin Server Returns Garbled Response After Connection Succeeds", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging "Error 520: web server returns an unknown error" — connection established but response is empty/malformed/reset?

For "Cloudflare Error 520 vs 522 vs 524 — Origin Server Returns Garbled Response After Connection Succeeds", collect the failing Cloudflare command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.