Skip to content

Fix Cloudflare Error 522 – Connection Timed Out & Origin

Cloudflare error 522 "Connection timed out"? Origin server offline, wrong IP, firewall blocking Cloudflare, SSL mode – fix step by step.

Domains & DNS

Quick answer: Cloudflare 522: make origin reachable (web service running, correct A record IP), don't block Cloudflare in firewall and check SSL mode (Full).

If you landed here: Browser shows "Error 522 – Connection timed out" with Cloudflare branding – site or subdomain unreachable.

5-minute checklist

  1. Test origin by IP directly – is web server running?
  2. Cloudflare DNS: A record points to current server IP?
  3. Server online? nginx/Apache + PHP-FPM active?
  4. Test grey cloud (DNS-only) temporarily – does it work?
  5. SSL/TLS: Full (strict) if origin certificate exists

Related

Products & ordering: Register a domain · Manage: NexoraHost · My account · nexorahost.com

Frequently asked questions (FAQ)

Cloudflare 522 – what does it mean?
Cloudflare can't reach your origin server (timeout). Server offline, wrong A record IP, firewall blocking Cloudflare IPs or web service (nginx/Apache) not running.
522 only with orange cloud (proxy)?
Yes – test DNS-only (grey cloud). If it works then: firewall must allow Cloudflare IP ranges or adjust SSL mode (Full vs Flexible).
522 after DNS migration?
Set A record in Cloudflare to new server IP, start origin service, wait 5–15 min. Check propagation with dnschecker.org.

Keep reading

Popular and fresh – not just the oldest guides.

More

Explore NexoraHost