Cloudflare Error 526: Invalid SSL certificate on the origin

Cloudflare completed the handshake with the origin but refused its certificate — expired, self-signed, or not matching the hostname — because the SSL mode is Full (Strict).

Short answer

Cloudflare completed the handshake with the origin but refused its certificate — expired, self-signed, or not matching the hostname — because the SSL mode is Full (Strict).

What Cloudflare Error 526 means

Full (Strict) validates the origin certificate. 526 means that validation failed. Switching to Full stops the error but also stops the validation, so it is a workaround rather than a fix.

Causes and fixes, most likely first

  1. The origin certificate expired. Renew the origin certificate and reload the origin's web server.
  2. The origin uses a self-signed certificate under Full (Strict). Install a Cloudflare Origin Certificate, which Full (Strict) trusts, or a publicly trusted certificate.
  3. The origin certificate does not cover the hostname. Reissue the origin certificate with the correct hostname in its SAN list.

How to stop it happening again

Check your own domain

The SSL check reports the origin certificate's expiry, issuer and covered hostnames — the three things Full (Strict) validates.

Frequently asked questions

Should I switch to Full to fix 526?

It removes the error but also removes origin certificate validation, leaving the Cloudflare-to-origin leg unauthenticated. Fix the origin certificate and stay on Full (Strict).