Cloudflare can't reach the origin
The origin server is down, overloaded, firewalling Cloudflare's IP ranges, or listening on a port Cloudflare does not proxy.
Origin reachable and proven
Working with Cloudflare?
Cloudflare sits between the public and your origin, which is a good place for it to help and an easy place for it to hide what is actually going wrong. We find the setting that is biting and leave the rest alone.
What it is
Cloudflare was founded in 2009 by Matthew Prince, Lee Holloway and Michelle Zatlyn, and now trades on the New York Stock Exchange under the ticker NET. It runs a reverse-proxy CDN, authoritative DNS and security service that sits in front of a large share of the public web, taking requests on your behalf and forwarding the ones it decides to trust.
The company has since grown well beyond DNS and caching. The platform now includes edge compute with Workers, object storage with R2, zero-trust access for internal apps, serverless hosting through Pages, video with Stream, and a domain registrar. Most customers only use a slice of all of that, rather than every product in the catalogue.
The honest version
No technology is all upside. This is where Cloudflare earns its place and where it tends to cause trouble.
Sound familiar?
The Cloudflare problems that bring people to us, and what you have once each one is fixed.
The origin server is down, overloaded, firewalling Cloudflare's IP ranges, or listening on a port Cloudflare does not proxy.
Origin reachable and proven
Flexible SSL rewrites HTTPS to HTTP at the edge while the origin forces HTTPS back again, so each side insists the other end is in the wrong.
SSL set to Full (strict)
The browser sees HTTPS, but Cloudflare talks to the origin in plain HTTP. Anyone between the edge and the server can read the traffic.
End-to-end encryption with a real cert
A firewall rule, a country block or a bot-fight setting is catching real users, often from a mobile network or a corporate VPN.
Rules that match attackers, not customers
Mail records cannot run through Cloudflare's proxy. An orange cloud on an MX, SPF or autodiscover record silently breaks mail.
Mail flowing, records corrected
A different Node version, a missing environment variable, or a build command that assumed a writable cache directory.
Deploys green and reproducible
A Worker doing too much synchronous work per request, or calling an origin that itself is slow, and hitting the CPU limit.
Within limits, with headroom
Years of page rules, firewall rules, workers and DNS entries added by people who have long since left, and no one on the current team wants to be the one to turn any of it off.
Account documented and trimmed
What we do
Call us for one broken setting, or hand us the whole account.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
A 522 means Cloudflare tried to reach your origin server and gave up waiting. Common causes are the origin being down or overloaded, a firewall on the origin blocking Cloudflare's IP ranges, or a hosting provider that has rate-limited the connection. The fix is almost always on the origin, not in the Cloudflare dashboard.
Nearly always because SSL is set to Flexible. Cloudflare serves HTTPS to the browser and sends HTTP to your origin, which then redirects back to HTTPS, which Cloudflare rewrites again. Switch SSL to Full (strict) and install a real certificate on the origin and the loop goes away.
It is not safe for anything that actually matters. Traffic between Cloudflare and your origin travels in plain text, so the padlock a visitor sees is misleading. Use Full (strict) with a certificate on the origin, which is free with Let's Encrypt or with a Cloudflare Origin Certificate.
Usually a firewall rule, a security level set too high, or a managed challenge catching mobile and VPN traffic. The dashboard's Security Events view shows exactly which rule triggered. We tune the rules so they catch attackers and not customers.
Copy every existing DNS record into Cloudflare first, with the orange cloud off on anything that is not plain web traffic, then change the nameservers at the registrar. Mail records, SIP, and any service with its own certificate must stay grey-clouded. We rehearse the move on a staging domain where that helps.
Estimates are free and come without any obligation. Tell us what is going wrong and you get a price before any changes are made to the account.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: