Cloudflare error · 525

Cloudflare error 525: SSL handshake failed

Cloudflare error 525 means the edge connected to your origin and the TLS handshake failed. Visitors using the proxied hostname never reach HTTP. 525 is Cloudflare’s code, not a registered HTTP status.

HTTP status codes explained · the longer reference on the blog.

What 525 means

Cloudflare’s SSL mode says the connection to the origin should be HTTPS. The origin then fails the handshake: it speaks plain HTTP on that port, it offers only an old TLS version, or the handshake is reset by a middlebox. The certificate’s name and expiry are the neighboring error, 526, which Cloudflare uses when the certificate is present but not acceptable in Full (strict) mode.

A browser that talks to the origin directly can show a different warning, or a normal page, depending on whether you bypass the proxy. The public hostname is what visitors and the homepage checker use. If that path is proxied, they see Cloudflare’s 525 page.

Common causes

  • The origin port speaks HTTP, and Cloudflare expects HTTPS

    SSL mode is Full or Full (strict), and port 443 is not TLS. The handshake fails immediately. Flexible mode avoids this and is a poor fix, because it leaves the origin hop unencrypted.

  • The origin and the edge share no TLS version or cipher

    An old device that only offers TLS 1.0, or a locked-down origin that disables what Cloudflare still sends. Both sides are “up” and still cannot negotiate.

  • A firewall interrupts the handshake

    Something allows the TCP connection and then drops or resets the TLS ClientHello. The result at the edge is a failed handshake, which Cloudflare reports as 525.

  • The wrong process is bound to 443

    A service that is not your web server answers the port and does not speak TLS. Local HTTP to port 80 still works, and the proxied HTTPS URL returns 525.

How to fix it

  • Decide the SSL mode and make the origin match it

    Full and Full (strict) need a real TLS listener on the origin. Install a certificate there, or use a Cloudflare origin certificate, and keep the mode on Full (strict) once the certificate is valid for the hostname.

  • Test TLS against the origin IP

    From outside, open a TLS connection to the origin on 443 and note the version and alert. A failure there is the same failure Cloudflare sees. A success there means the edge is aimed at a different port or host.

  • Enable a current TLS version on the origin

    Turn on TLS 1.2 or newer on the web server. Then retry the public URL. Leave ancient protocols off.

  • Point 443 at the web server

    Confirm the process listening on 443 is nginx, Caddy, or whatever terminates TLS for this site. Reload it after the certificate and port are correct.

Is it your site, or just you?

525 is generated for traffic through Cloudflare. A second network seeing the same page means the public hostname is failing the handshake for visitors, not only for your browser.

The homepage checker requests the public URL. HTTP 525, or an SSL error from the checker, means the proxied path is failing from our network. The checker also reports SSL issuer and days remaining when a certificate is visible on the hostname it could inspect.

How to monitor for 525

Monitor the https URL and expect 200. A 525 fails the check like any other unexpected status, and the alert includes that code. ismysiteup also tracks SSL certificate expiry on monitored HTTPS URLs and can warn before a certificate lapses. Expiry warnings and a 525 are different faults: 525 means the handshake is already failing.

The checker on the ismysiteup homepage requests the URL from our servers and shows the HTTP status, response time, and SSL details. No account is required, and that checker allows 5 checks per hour from the same network. A free account watches 5 URLs, each checked every 10 minutes, and sends alerts on WhatsApp, Telegram, Slack, or email. A monitor expects HTTP 200 unless you set a different expected status (100–599). One failed check is confirmed with a second check before the first alert, and a later success sends a recovery alert. Pro (every 5 minutes) and Business (every minute) are listed on the pricing page; paid checkout is not open yet.

Compare Free, Pro, and Business

Related status codes

FAQ

What does Cloudflare error 525 mean?

The TLS handshake between Cloudflare and your origin failed. Visitors did not get an HTTP response from your application.

How is 525 different from 526?

525 is a handshake that did not complete. 526 means the handshake got far enough for Cloudflare to reject the origin certificate, usually in Full (strict) mode.

Does the free monitor see 525?

Yes. It requests the public URL on its schedule, every 10 minutes on the free plan, and treats 525 as a failed check when it expects 200.