Cloudflare reached your server but could not complete a TLS handshake with it. It happens only when Cloudflare is set to connect to the origin over HTTPS — Full or Full (strict) — and the server has no working certificate or TLS setup on port 443.
Error 525 SSL handshake failed
| Error | Error 525 SSL handshake failed |
| Usually fixed by | The website |
| Shown by | Cloudflare, instead of your site |
| Happens in | SSL/TLS mode Full or Full (strict) |
| Between | Cloudflare and your server — not the visitor |
Check the certificate a site serves
Cloudflare answers for your domain, so this checks Cloudflare’s certificate; to test your server itself, connect to its IP address with openssl s_client (below).
What it means
With a proxied record, visitors connect to Cloudflare, and Cloudflare connects to your server. In Full and Full (strict) modes that second connection uses HTTPS; 525 means its handshake failed before any request was made.
Why it happens
- No valid SSL certificate installed on the origin server.
- Port 443 is not open on the origin, or a firewall blocks Cloudflare’s addresses.
- The origin does not support SNI.
- The cipher suites the origin accepts do not match those Cloudflare uses.
How to fix it
- Install a certificate on the origin — a Cloudflare Origin CA certificate is free and trusted by Cloudflare — and make sure the server listens for TLS on 443.
- Check the origin’s TLS settings: SNI support and modern cipher suites.
- Read the origin web server’s error log at the time of the error.
See it for yourself
openssl s_client -connect 203.0.113.10:443 -servername example.com
Connect to your origin’s IP address (not the Cloudflare one) with your domain as the server name: a failure here is the failure Cloudflare sees.
Questions
Should I switch Cloudflare to Flexible to get rid of 525?
No. Flexible leaves the connection to your server unencrypted and invites redirect loops; Cloudflare strongly recommends Full or Full (strict). Install a certificate on the origin instead.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- Error 525 — developers.cloudflare.com
- Encryption modes — developers.cloudflare.com
- Cloudflare origin CA — developers.cloudflare.com