Skip to content
Help Centre

Fix “Not Secure” warnings and a missing padlock

Why browsers warn about your site, and how to fix mixed content.

1 min read Updated

“Not Secure” on every page

  • No certificate yet: check SSL/TLS Status.
  • Visitors are using http://: force HTTPS.
  • Certificate expired: free SSL renews automatically if the domain still points to us. Paid certificates must be renewed and reinstalled.

“Your connection is not private” (NET::ERR_CERT…)

  • The certificate doesn’t cover the exact address being visited, e.g. it covers yourdomain.co.bw but not shop.yourdomain.co.bw. Run AutoSSL again, or use a Wildcard certificate.
  • The domain recently moved, and the old server is still being reached. Wait for propagation.
  • The computer’s date and time are wrong. Correct them and try again.

Padlock missing on some pages (mixed content)

The page loads over HTTPS, but some images, scripts or stylesheets still load over http://.

  1. Open the page in Chrome, press F12, and look at the Console tab for “Mixed Content” warnings. They name the files.
  2. Change those links to https://.
  3. WordPress: after switching your site address to https, update old links in your content with a search-and-replace plugin (replace http://yourdomain.co.bw with https://yourdomain.co.bw), and take a backup first.

Still seeing a warning? Open a ticket with the page address and a screenshot.

Was this article helpful?

Related articles