What 526 means
Unofficial, used by Cloudflare. In Full (strict) SSL mode, Cloudflare couldn’t validate the certificate on the website’s own server.
When servers send it
When the origin certificate has expired, is self-signed (and not a Cloudflare Origin CA certificate), or doesn’t match the host name.
Common causes
- An expired origin certificate.
- A self-signed certificate.
- A certificate for a different host name.
- A missing intermediate certificate.
How to fix it as a developer
- Renew or replace the origin certificate. A Cloudflare Origin CA certificate is trusted in Full (strict) mode.
- Make sure the certificate covers the host name Cloudflare connects with.
- Check the chain with
openssl s_client -showcerts.
How to fix it as a visitor
- Try again later. The site’s certificate needs fixing by its owner.
Related codes
- 525 SSL Handshake Failed: Cloudflare couldn’t set up a secure (TLS) connection with the website’s server.
- 520 Web Server Returned an Unknown Error: Cloudflare reached the website’s server but got back an empty, unknown or unexpected response.
- 495 SSL Certificate Error: nginx couldn’t verify the client certificate the browser presented. Sent to the browser as 400.
Where it’s defined
526 isn’t in any RFC or the IANA status code registry. It’s used by Cloudflare. Reference: Cloudflare docs: error 526.
Other 5xx codes
500 Internal Server Error · 501 Not Implemented · 502 Bad Gateway · 503 Service Unavailable · 504 Gateway Timeout · 505 HTTP Version Not Supported · 511 Network Authentication Required · 520 Web Server Returned an Unknown Error · 521 Web Server Is Down · 522 Connection Timed Out · 523 Origin Is Unreachable · 524 A Timeout Occurred · 525 SSL Handshake Failed
Or search them all in the HTTP status code list.