HTTP 525 SSL Handshake Failed

Non-standard, from Cloudflare: the TLS handshake between the CDN and the origin failed — no common cipher, no certificate, or a misconfigured TLS listener.

Non-standard — not defined by any RFC. Vendor documentation: Cloudflare 5xx error reference

Where you meet HTTP 525 in production

Right after enabling HTTPS between the CDN and the origin, after a TLS configuration change on the origin, or when the origin's TLS listener is missing on the expected port.

Why you would test it

A deploy-time failure more than a runtime one. Smoke tests after a certificate or TLS change should hit the public hostname, where this appears, not the origin directly.

What your client should do about a 525

Nothing a client can retry its way out of. Treat it as an outage, and on the operations side add a post-deploy smoke test against the public hostname so a TLS mismatch is caught before users find it.

525 versus the codes it gets confused with

Endpoints that return 525

1 endpoint in this playground answers with 525. Every one is free, needs no signup, and can be called from the browser or with curl.

Questions about HTTP 525

Is my visitor's certificate the problem?
No. This is the connection between the CDN and your origin, not between the visitor and the CDN.
How do I test for it?
Run a smoke test through the public hostname after every TLS or certificate change.

Other server error codes

All HTTP status codes · All 55 mock REST APIs · Getting started guide

Last updated