What 525 means
Unofficial, used by Cloudflare. The secure (TLS) handshake between Cloudflare and the website’s own server failed.
When servers send it
When the site uses Cloudflare’s Full or Full (strict) SSL mode and the origin can’t complete a TLS handshake.
Common causes
- No certificate installed at the origin, or HTTPS not set up on port 443.
- The origin not supporting SNI or any cipher Cloudflare offers.
- A firewall interfering with port 443.
How to fix it as a developer
- Make sure the origin serves HTTPS on port 443 with a certificate. A free Cloudflare Origin CA certificate works.
- Test the handshake directly with
openssl s_client -connect origin:443 -servername example.com. - Check the origin supports modern TLS versions and ciphers.
How to fix it as a visitor
- Try again later. The site has a configuration problem.
Related codes
- 526 Invalid SSL Certificate: Cloudflare couldn’t validate the certificate on the website’s server.
- 520 Web Server Returned an Unknown Error: Cloudflare reached the website’s server but got back an empty, unknown or unexpected response.
- 502 Bad Gateway: A proxy or load balancer got an invalid response, or none at all, from the server behind it.
Where it’s defined
525 isn’t in any RFC or the IANA status code registry. It’s used by Cloudflare. Reference: Cloudflare docs: error 525.
Other 5xx codes
500 Internal Server Error · 501 Not Implemented · 502 Bad Gateway · 503 Service Unavailable · 504 Gateway Timeout · 505 HTTP Version Not Supported · 511 Network Authentication Required · 520 Web Server Returned an Unknown Error · 521 Web Server Is Down · 522 Connection Timed Out · 523 Origin Is Unreachable · 524 A Timeout Occurred · 526 Invalid SSL Certificate
Or search them all in the HTTP status code list.