Introduction
A Cloudflare 525 error means Cloudflare successfully reached the origin server but could not complete the SSL handshake. The edge is up, the hostname resolves, and traffic reaches the server, but the TLS session between Cloudflare and the origin fails before HTTP begins.
Symptoms
- Cloudflare displays a
525 SSL handshake failedpage - The issue affects proxied traffic but may not appear when testing the origin directly over HTTP
- The problem started after changing origin certificates or SSL modes
- Some hostnames work while one proxied hostname fails
- Origin logs show TLS negotiation failures or rejected connections
Common Causes
- The origin certificate is expired, missing, or invalid for the hostname
- Cloudflare is set to Full or Full (strict) but the origin TLS setup is incomplete
- The origin server does not support required TLS versions, ciphers, or SNI behavior
- Firewall or security rules block Cloudflare IP ranges during TLS negotiation
- A load balancer or reverse proxy serves the wrong certificate to Cloudflare
Step-by-Step Fix
- Confirm the Cloudflare SSL mode in the dashboard and compare it with the actual certificate state on the origin.
- Test the origin directly over HTTPS using the same hostname to inspect the certificate, chain, and protocol support.
- Verify the certificate on the origin is valid, unexpired, and covers the exact hostname Cloudflare is proxying.
- Check whether the origin supports modern TLS versions and SNI, especially on shared hosting or older web server builds.
- Review firewall rules, server security software, and upstream rate limits to ensure Cloudflare IP ranges are not blocked.
- If a load balancer or secondary proxy sits in front of the app, confirm it presents the correct certificate on port 443.
- Replace or install the correct origin certificate and reload the relevant service after the change.
- Re-test through Cloudflare and verify the 525 page disappears for the affected hostname.
- Keep certificate renewal, Cloudflare SSL mode, and origin TLS settings documented together so later changes stay aligned.