# SSL certificates and HTTPS issues: a fix list

URL: https://ekom.blog/ssl-certificates-and-https-issues-a-fix-list/
Published: 2023-12-04 · Updated: 2026-11-03
Author: Ekom
Topics: Web management

> Browser warnings, redirect loops, mixed content and certificates that quietly expire. The HTTPS problems I see most on client sites, how to tell which one you have, and how to fix each one.

The message usually comes in a panic. "The site says Not secure." Or worse: "Customers are getting a big red warning and can't get in."

HTTPS problems feel scary because the browser makes them look scary. That's the point of the warnings. But most of them come from a handful of causes, and once you know which one you're looking at, the fix is usually quick.

Looking after DNS, SSL and Cloudflare for client sites is part of my job at Nivonix, so these come up regularly. Here's the list I work through.

## First, read the error properly

Browsers tell you more than you'd think. Before changing anything, note exactly what you see, in which browser, on which address (with or without www, http or https).

The common ones:

- "Not secure" in the address bar, but the page loads: usually mixed content, or the page loaded over plain http.

- "Your connection is not private" / NET::ERR_CERT_DATE_INVALID: the certificate has expired, or the device's clock is wrong.

- NET::ERR_CERT_COMMON_NAME_INVALID: the certificate doesn't cover the address you're visiting (often www vs non-www, or a subdomain).

- ERR_TOO_MANY_REDIRECTS: a redirect loop, very often a Cloudflare SSL setting.

- ERR_SSL_PROTOCOL_ERROR or a handshake failure: the server isn't serving a valid certificate at all, or something in between is misconfigured.

Clicking the padlock (or the warning) in the address bar shows the certificate's details: who issued it, which domains it covers, and when it expires. That alone solves half of these.

## 1. The certificate has expired

The most common cause, and the most avoidable.

Free certificates from Let's Encrypt last 90 days and renew automatically. That's great until the automatic renewal fails. It can fail because DNS moved, a firewall blocks the validation request, the hosting account changed, or a cPanel setting was switched off.

Fix:

- In cPanel, open SSL/TLS Status (or AutoSSL) and run the renewal. It usually tells you why it failed if it can't.

- If the domain's DNS now points somewhere else (Cloudflare, a new host), the old host can't validate the domain. Issue the certificate where the traffic actually lands.

- Paid certificates need renewing and reinstalling manually. Put the expiry date in a calendar with a reminder a month before.

Prevent it: an uptime monitor that also checks certificate expiry. I covered mine in the uptime monitoring setup I use for client sites.

## 2. The certificate doesn't cover this address

A certificate is issued for specific names. If it covers example.com but not www.example.com, anyone typing www gets a warning.

Fix: reissue the certificate to include every version people use: the root domain, www, and any subdomains like shop. or blog.. Then make sure only one version is your main address and the others redirect to it.

## 3. Mixed content

The page itself loads over HTTPS, but some images, scripts or stylesheets on it still load over http://. Browsers either block those files or downgrade the padlock.

It's very common after moving a WordPress site to HTTPS, because old posts have image URLs saved with http:// in the database.

Find it: open the browser's developer tools (right-click → Inspect → Console). Mixed content warnings list each insecure file.

Fix on WordPress:

- Make sure Settings → General shows https:// for both the WordPress Address and Site Address.

- Run a search and replace on the database from http://yourdomain.com to https://yourdomain.com. Use a plugin like Better Search Replace, and take a backup first (my backup setup is here). Do a dry run before the real one.

- Check the theme and any custom code for hard-coded http:// links.

- Fix external scripts that only exist on http. If a provider doesn't support HTTPS in 2023, that's a sign to replace them.

Cloudflare's "Automatic HTTPS Rewrites" can help cover the gaps, but I treat it as a safety net, not the fix.

## 4. Redirect loops with Cloudflare

This one confuses a lot of people. The site worked, you switched on Cloudflare, and now the browser says the page redirected too many times.

The usual cause is Cloudflare's Flexible SSL mode. In Flexible mode, Cloudflare talks to visitors over HTTPS, but to your server over plain HTTP. If your server (or WordPress, or an SSL plugin) redirects HTTP to HTTPS, every request bounces: Cloudflare asks over HTTP, the server says "go to HTTPS", Cloudflare asks over HTTP again, and round it goes.

Fix: install a valid certificate on the origin server (a free one from the host, or a Cloudflare Origin Certificate), then set Cloudflare's SSL/TLS mode to Full (strict). Flexible should almost never be your long-term setting. I explained the modes in more detail in DNS, SSL and Cloudflare: what site owners should know.

Other redirect loop causes:

- two plugins (or a plugin and the server) both forcing HTTPS in different ways

- a redirect rule in .htaccess that conflicts with one in Cloudflare

- WordPress Address and Site Address set to different versions of the domain

Clear the browser cache (or test in a private window) after each change. Browsers remember redirects.

## 5. HTTP still loads instead of redirecting

If http://yourdomain.com loads the page without redirecting to HTTPS, you have two versions of the site. Google may treat them as duplicates, and visitors on the old links never get the padlock.

Fix: a single site-wide 301 redirect from HTTP to HTTPS. Most hosts have a "Force HTTPS" toggle. Cloudflare has "Always Use HTTPS". Pick one place to do it, not three, so you don't create the loops above.

## 6. HSTS surprises

HSTS tells browsers "only ever use HTTPS for this site". It's a good security setting. It also means that if the certificate breaks, visitors can't click past the warning at all, and browsers remember the setting for as long as you told them to.

My rule: only enable HSTS once HTTPS has been stable for a while, start with a short max-age, and don't tick "include subdomains" or "preload" unless every subdomain is ready for HTTPS. Undoing a preload is slow.

## 7. It works for you but not for them

If the site is fine on your laptop but a client or customer still sees a warning:

- check their device's date and time (a wrong clock makes valid certificates look expired)

- ask them to try a private window or another browser

- remember DNS changes can take time to reach everyone, so some people may still be hitting the old server and its old certificate

- corporate networks and antivirus software sometimes intercept HTTPS and cause their own warnings

## The SEO side

HTTPS is a light ranking signal, but the bigger SEO risk is broken access. If Googlebot hits certificate errors, it can't crawl properly, and visitors who see warnings leave. After fixing anything here:

- make sure Search Console is set up as a domain property, which covers both protocols

- check that your sitemap and canonical tags use https://

- spot-check a few important URLs with the URL Inspection tool

## Related reading

- DNS, SSL and Cloudflare: what site owners should know

- Cloudflare settings that help speed and security

- Hosting migrations without losing rankings

- The uptime monitoring setup I use for client sites

Click the padlock on your own site right now and check the expiry date. If it's a paid certificate, put that date in your calendar today.

---

From Ekom (https://ekom.blog/). More: https://ekom.blog/llms.txt
