Visitors: wait a few minutes and reload; it's not your device. Site owners: check the origin server is up and not overloaded, the DNS A/AAAA records in Cloudflare point to the correct IP, and the server firewall allows Cloudflare's IP ranges on ports 80/443.

What Error 522 actually means

Cloudflare sits between visitors and the website. A 522 means the TCP connection to the origin didn’t complete (no SYN-ACK within ~15 seconds), so it’s a server-side or hosting problem, not the visitor’s browser.

What you'll see

  • Cloudflare page: “Error 522. Connection timed out” with Browser/Cloudflare working and Host error.

What causes Error 522

  • Origin server down or overloaded.
  • Firewall blocking Cloudflare IPs.
  • Wrong origin IP in DNS.
  • Hosting network problems.

How to fix it

  1. VisitorsReload after a few minutes; check whether others report the site down.
  2. Check the originConfirm the server is running and responsive (SSH, hosting panel, uptime monitor).
  3. Check DNS recordsIn Cloudflare DNS, make sure the A/AAAA records point to the current server IP.
  4. Allow Cloudflare IPsWhitelist Cloudflare's published IP ranges in server firewalls, fail2ban and security plugins.
  5. Check resources and KeepAliveReduce load, increase resources, and make sure KeepAlive is enabled on the web server.
How to tell it worked: The site loads through Cloudflare without the 522 page.

Stop it happening again

Monitor origin uptime and keep firewall rules updated with Cloudflare's IP ranges.