HTTP 526 Invalid SSL Certificate

Non-standard, from Cloudflare: the origin presented a certificate the CDN would not accept under strict validation — expired, self-signed or for the wrong host.

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

Where you meet HTTP 526 in production

When an origin certificate expires, is self-signed, or does not cover the hostname, and the CDN is configured to validate the origin certificate strictly. It typically appears on the day a renewal failed.

Why you would test it

Add a certificate-expiry check to monitoring; a 526 on the day a certificate lapses is the symptom of a renewal that did not happen.

What your client should do about a 526

Treat it as an outage; retries will not help until the certificate is fixed. Operationally, monitor certificate expiry with enough warning to renew, and test renewals in a staging environment that also validates strictly.

526 versus the codes it gets confused with

Endpoints that return 526

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

Questions about HTTP 526

Why did it start suddenly?
Most often the origin certificate expired.
Can I just disable validation?
You can, and it removes the protection validation exists for. Renew the certificate instead.

Other server error codes

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

Last updated