Cloudflare / Cloudflare

Cloudflare Error 522 Origin Connection Timed Out: TCP Handshake Fails Between Edge and Origin Server

Diagnose and fix Cloudflare 522 errors where origin server doesn't respond to TCP handshake — caused by server overload, firewall blocking Cloudflare IPs, KeepAlive disabled, or DNS misconfiguration Includes evidence for Cloudflare troubleshooting demand.

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

Category: Cloudflare
Error signature: Error 522: connection timed out — Cloudflare times out contacting the origin web server within ~15 seconds, TCP handshake never establishes
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: June 1, 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 522: connection timed out — Cloudflare times out contacting the origin web server within ~15 seconds, TCP handshake never establishes is a Cloudflare failure pattern reported for developers trying to diagnose and fix cloudflare 522 errors where origin server doesn't respond to tcp handshake — caused by server overload, firewall blocking cloudflare ips, keepalive disabled, or dns misconfiguration. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Sources: Cloudflare official docs (updated May 15 2026), contabo.com blog, elementor.com guide. Error 522 means TCP connection between Cloudflare edge and origin never completes — unlike 524 where connection succeeds but response is slow. Causes: overloaded origin, firewall blocking CF IPs, incorrect DNS/IP, disabled KeepAlive. Very high volume daily search, blocks production websites.

Common causes

Sources: Cloudflare official docs (updated May 15 2026), contabo.com blog, elementor.com guide. Error 522 means TCP connection between Cloudflare edge and origin never completes — unlike 524 where connection succeeds but response is slow. Causes: overloaded origin, firewall blocking CF IPs, incorrect DNS/IP, disabled KeepAlive. Very high volume daily search, blocks production websites.

Quick fixes

Confirm the exact error signature matches Error 522: connection timed out — Cloudflare times out contacting the origin web server within ~15 seconds, TCP handshake never establishes.
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 522: connection timed out — Cloudflare times out contacting the origin web server within ~15 seconds, TCP handshake never establishes 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 522: connection timed out — Cloudflare times out contacting the origin web server within ~15 seconds, TCP handshake never establishes mean in Cloudflare?

Error 522: connection timed out — Cloudflare times out contacting the origin web server within ~15 seconds, TCP handshake never establishes indicates the workflow described by "Cloudflare Error 522 Origin Connection Timed Out: TCP Handshake Fails Between Edge and Origin Server" failed in a Cloudflare context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Error 522: connection timed out — Cloudflare times out contacting the origin web server within ~15 seconds, TCP handshake never establishes?

Check whether this cause matches your environment: Sources: Cloudflare official docs (updated May 15 2026), contabo.com blog, elementor.com guide. Error 522 means TCP connection between Cloudflare edge and origin never completes — unlike 524 where connection succeeds but response is slow. Causes: overloaded origin, firewall blocking CF IPs, incorrect DNS/IP, disabled KeepAlive. Very high volume daily search, blocks production websites.

Is the Error 522: connection timed out — Cloudflare times out contacting the origin web server within ~15 seconds, TCP handshake never establishes guidance source-backed?

The "Cloudflare Error 522 Origin Connection Timed Out: TCP Handshake Fails Between Edge and Origin Server" page is labeled source-backed. It has 3 public source URLs from developers.cloudflare.com, contabo.com, elementor.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Error 522: connection timed out — Cloudflare times out contacting the origin web server within ~15 seconds, TCP handshake never establishes?

For "Cloudflare Error 522 Origin Connection Timed Out: TCP Handshake Fails Between Edge and Origin Server", 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 522: connection timed out — Cloudflare times out contacting the origin web server within ~15 seconds, TCP handshake never establishes?

For "Cloudflare Error 522 Origin Connection Timed Out: TCP Handshake Fails Between Edge and Origin Server", 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.