Blog Details

  • Home
  • Blog
  • Blog
  • Invalid SSL Certificate Error Code 526: What It Means and How to Fix It
Invalid SSL Certificate Error Code 526: What It Means and How to Fix It

Invalid SSL Certificate Error Code 526: What It Means and How to Fix It

Error 526 means Cloudflare can’t verify the SSL certificate on your origin server. It only appears when your SSL/TLS mode is set to Full (strict). The usual causes are an expired, self signed, wrong hostname or incomplete certificate. Fix it by installing a valid certificate, or a free Cloudflare Origin CA certificate, on your server and reloading it.

You type in your own website address and, instead of the homepage, a Cloudflare page tells you “Error 526: Invalid SSL certificate”. No slow warning signs, just a wall.

Take a breath. It looks worse than it is. Error 526 is one of the more fixable errors you’ll run into, because it points at one specific thing: the SSL certificate sitting on your hosting server. Below you’ll find what the error means, how to work out which problem you’ve got, and how to fix it in a sensible order. We’ll also flag the popular quick fix that shouldn’t stay switched on.

What Does Error 526 Invalid SSL Certificate Mean?

Error 526 means Cloudflare reached your hosting server but refused to trust the SSL certificate it found there. Cloudflare’s error 526 documentation says it happens when two things are true: Cloudflare can’t validate the certificate on your origin web server, and your SSL/TLS mode is Full (strict).

Think of your site as having two separate connections. One runs from your visitor’s browser to Cloudflare. The other runs from Cloudflare to your origin server, the machine at your host where the website files actually live. A visitor can have a healthy padlock on the first leg and still hit a 526, because the failure is on the second leg, out of their sight.

Full (strict) is the mode that checks the certificate properly. Plain Full accepts almost any certificate, even a dodgy one, which is why the error never appears there.

What Causes Error 526?

Five problems cause nearly every 526: an expired certificate, a self signed one, a certificate for the wrong hostname, a missing intermediate chain, or a revoked certificate. Here’s how each one tends to show up.

Cause What’s going on Usual fix
Expired certificate The end date has passed, often because auto renewal quietly failed Renew it and reload the server
Self signed certificate The server made its own certificate, so no trusted authority vouches for it Install a trusted certificate or a Cloudflare Origin CA certificate
Wrong hostname It covers www.example.com.au but not example.com.au, or skips a subdomain Reissue it to cover every hostname you proxy
Missing intermediate chain The server sends your certificate but not the chain linking it to a trusted authority Install the full chain file
Revoked certificate The issuer has cancelled it Issue a new one

Timing is a clue too. If a site has run happily for years on a self signed certificate and someone then raises Cloudflare to Full (strict), the certificate was never really valid. Strict mode just started checking.

How Do You Check Which Certificate Problem You Have?

Look at the certificate your origin server is actually serving, not the one Cloudflare shows visitors. Cloudflare’s documentation suggests temporarily pausing Cloudflare and running your domain through an SSL checker. You can also test the origin directly from your own computer.

  1. Find your origin IP. Your hosting control panel shows it. Cloudflare’s DNS tab only shows its own proxy addresses.
  2. Run a quick check. In a terminal with OpenSSL installed, run the command below, swapping in your origin IP and domain.
  3. Read the result. Look at the end date, the issuer and the names the certificate covers.

openssl s_client -connect ORIGIN_IP:443 -servername yourdomain.com.au | openssl x509 -noout -subject -issuer -dates

If you’d rather not use a terminal, the Qualys SSL Labs server test reports expiry dates and chain problems in plain language. Switch the DNS record to “DNS only” first, otherwise it tests Cloudflare’s certificate and tells you nothing about your server.

How Do You Fix Error 526?

You fix error 526 by correcting the certificate on your origin server. The usual order is to renew or replace the certificate, use a Cloudflare Origin CA certificate if the site is only reached through Cloudflare, and treat switching modes as a short term stopgap.

Renew or reinstall a valid certificate

If the certificate has expired or is missing its chain, get a fresh one and install it with the full chain. On cPanel hosting, AutoSSL or a Let’s Encrypt certificate usually takes care of this, and Let’s Encrypt is a free, widely trusted authority. On Nginx, point ssl_certificate at the full chain file rather than the bare certificate. Apache 2.4.8 and newer accepts the chain in the same file as the certificate. Reload the web server afterwards, or nothing changes.

Install a Cloudflare Origin CA certificate

For sites that visitors only ever reach through Cloudflare, an Origin CA certificate is often the cleanest fix. You create it in the Cloudflare dashboard under SSL/TLS, then Origin Server, and install the certificate and private key on your server. Cloudflare’s Origin CA documentation covers the details. It’s free and can last up to 15 years.

There’s one catch. Browsers don’t trust Origin CA certificates, so keep the Cloudflare proxy switched on. If someone reaches your server directly, they’ll see a security warning.

Switch from Full (strict) to Full, then switch back

Changing the mode from Full (strict) to Full clears the error almost immediately, and Cloudflare itself lists it as a quick fix. The price is that Cloudflare stops checking whether your server’s certificate is genuine. Treat it like a tourniquet. Use it to get the site back, fix the certificate properly, then put Full (strict) back on.

Please don’t reach for Flexible instead. That sends traffic from Cloudflare to your server unencrypted, and on WordPress it can also cause redirect loops.

Ask your host

If you don’t have access to the server settings, ask your host to confirm the certificate isn’t expired or revoked and that the server accepts connections on port 443. Send them the exact error and the time you saw it.

Why Does Error 526 Appear After a WordPress Migration?

Why Does Error 526 Appear After a WordPress Migration?

It usually happens because the new server doesn’t have a valid certificate yet, while Cloudflare is already pointing at it in Full (strict) mode. The old host had a working certificate. The new one hasn’t issued one, or has issued one for a temporary hostname.

It’s a classic chicken and egg problem. Many hosts can only issue a certificate once the domain points at them, but the domain points at Cloudflare, which refuses to talk to a server without a valid certificate. The way out is to use an Origin CA certificate, or to drop to Full for an hour while the proper certificate is issued.

Moves like this are routine in any web design Sydney project, which is why SSL belongs on the go live checklist before DNS changes. We cover the full process in our guide on how to manually migrate a WordPress site.

How Do You Stop Error 526 Coming Back?

Make sure your certificate renews automatically, covers every hostname you proxy, and is monitored by something other than hope. A few habits do most of the work.

  • Cover every hostname. Include the root domain, www and any subdomain behind Cloudflare. The forgotten subdomain is a classic second day 526.
  • Test after changing modes. After moving to Full (strict), load every proxied hostname, not just the homepage.
  • Watch expiry dates. Auto renewal can fail without telling anyone, so set a reminder or use an uptime monitor that checks certificates.
  • Know who owns renewal. Write down where each certificate was issued and who is responsible for it.

Good Website Maintenance Services include certificate checks alongside updates and backups, so a lapsed certificate gets caught before your customers see it. If you’re planning a rebuild, make sure whoever handles your Website Design Australia project also owns hosting, SSL and Cloudflare settings, so nobody assumes somebody else is watching the certificate.

If you’d rather not play detective, Systronic IT Group can check your origin certificate, Cloudflare settings and WordPress setup, then fix the cause properly. Contact our team and tell us the error you’re seeing.

Error 526 FAQs

Is error 526 my fault or Cloudflare’s?

Almost always it’s the origin certificate, not Cloudflare. Cloudflare reached your server, looked at the certificate and rejected it. That means the fix sits with whoever manages your hosting or SSL, even if the error page carries Cloudflare’s name.

What is the difference between error 525 and error 526?

Error 525 means the secure handshake between Cloudflare and your server failed outright. Error 526 means the handshake worked but the certificate didn’t pass validation under Full (strict). In short, 525 is about the connection and 526 is about the certificate.

Can I fix error 526 without access to my server?

Partly. If you control Cloudflare, you can switch the mode from Full (strict) to Full to get the site back. That’s only a stopgap. The proper fix needs a valid certificate on the origin, so you’ll need your host or developer to install one.

Does error 526 hurt my SEO?

A short outage rarely does lasting damage, but a long one can. Search engines treat 5xx responses as server errors, and if they persist, crawlers slow down and visitors bounce. Fix it quickly and check that your key pages load normally afterwards.

Is a Cloudflare Origin CA certificate enough on its own?

It’s enough for traffic that passes through Cloudflare, because Cloudflare trusts it. Browsers don’t, so it isn’t suitable if you turn the Cloudflare proxy off or let people reach the origin directly. In that case, use a publicly trusted certificate.

Why does error 526 only appear on one subdomain or the WordPress admin?

The certificate probably doesn’t cover that hostname. A certificate for example.com.au won’t automatically cover shop.example.com.au. Reissue it to include every hostname you proxy, or use a wildcard certificate, then reload the server.

Cart

No products in the cart.