
The short answer: a 52x error carrying Cloudflare’s name means Cloudflare arrived, but could not talk to your server (or talked badly). The site itself may or may not be fine: the number says where to look. The most common are 521 (server refuses), 522 (does not answer in time), 525 and 526 (certificate problems).
What the site needs
| What | What to do |
| 520 | An empty or odd answer from the server. A program that fails halfway or a firewall cutting off. |
| 521 | The server refused the connection: it is stopped, or a firewall blocks Cloudflare. |
| 522 and 524 | The server did not answer in time (522) or took too long to answer (524): slow, overloaded or unreachable. |
| 523 | Cloudflare cannot find the server: the IP address in the DNS is wrong or has changed. |
| 525 and 526 | The encryption handshake failed (525) or the server’s certificate is invalid (526). It has to do with the SSL mode: Switching on SSL at Cloudflare. |
Getting started
|
|
|
|
|
| Do not leave Cloudflare on “DNS only” for good out of tiredness. You lose the protection and the cache. Find the cause and turn the proxy back on. And be careful changing the SSL mode blindly: Redirect loops. |
| When Cloudflare helps and when it gets in the way: Cloudflare, and the options that cause work: The options worth having. |
|
A 52x error that will not go away? Open a ticket with the address and the exact number. Open a support ticket |
RECOMMENDED PRODUCT Web hosting with cPanel Domain and SSL included, daily backups and the panel you already know. from $6.59/mo (3-year plan, with coupon) See plans |
- 0 Users Found This Useful











