Cloudflare error · 526

Cloudflare error 526: invalid SSL certificate

Cloudflare error 526 means the edge completed enough of the TLS handshake to inspect your origin certificate, then refused it. In Full (strict) mode the certificate must be valid for the hostname. 526 is Cloudflare’s code, not a registered HTTP status.

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

What 526 means

Cloudflare is protecting visitors from an origin certificate it does not trust. The usual reasons are expiry, a name that does not match the hostname, a self-signed certificate, or a chain the edge cannot build. The origin web server can be healthy. HTTPS between Cloudflare and the origin is what failed validation.

Error 525 is the earlier failure, where the handshake never gets as far as a certificate Cloudflare can judge. A browser pointed directly at the origin shows the same certificate problem as a warning, which is a useful confirmation. The public proxied URL shows 526 instead of that browser warning.

Common causes

  • The origin certificate expired

    Renewal did not run, or it renewed a different certificate than the one the web server loads. Full (strict) starts returning 526 at expiry.

  • The certificate name does not match

    The cert is for www and the origin hostname is the apex, or it is for a previous domain. Name mismatch is an invalid certificate for this URL.

  • The certificate is self-signed or the chain is incomplete

    Full (strict) requires a publicly trusted chain or a Cloudflare origin certificate. A self-signed cert, or a missing intermediate, fails that test.

  • The server is still using the old file

    A renewed certificate is on disk, and the process was not reloaded. The edge keeps seeing the previous, invalid certificate.

How to fix it

  • Read the certificate the origin actually serves

    Inspect the certificate on the origin port: subject names, expiry, and issuer. Trust that output over the file you think is configured.

  • Install a certificate that matches the hostname

    Use a public CA certificate for that name, or a Cloudflare origin certificate, and include the intermediate chain. Then reload the web server.

  • Keep Full (strict) once the certificate is valid

    Dropping to Full hides 526 by skipping name validation. It also hides a hostname mismatch you still want to know about. Fix the certificate and leave strict validation on.

  • Reload after renewal

    Confirm the listener picked up the new files. Request the public URL again. A 200 means Cloudflare accepted the origin certificate.

Is it your site, or just you?

526 is the same for every visitor through the proxy. Check on a phone off your Wi-Fi. If they see it, the origin certificate is being rejected for the public site.

The homepage checker loads the public URL and, when it can read a certificate, shows the issuer and how many days remain. A 526 from the checker means the proxied path is failing from our network. Compare that with a direct look at the origin certificate.

How to monitor for 526

Monitor the https URL and expect 200. HTTP 526 fails the check and alerts after a second consecutive failure. The same monitors also watch SSL expiry and can warn you before the certificate runs out, which is the failure you want to catch earlier than a 526. Free accounts get 5 monitors, checked every 10 minutes.

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 526 mean?

Cloudflare did not accept the origin certificate. Expiry, a wrong hostname, a self-signed cert, or a broken chain are the usual reasons in Full (strict) mode.

How is 526 different from 525?

525 means the TLS handshake failed before a usable certificate check. 526 means Cloudflare saw a certificate and judged it invalid.

Can monitoring warn me before a 526?

An expiry warning can. ismysiteup checks the certificate on a monitored HTTPS URL and can alert as it nears expiry. A 526 still alerts as downtime if the public URL starts returning that status.