Home › Knowledgebase › KB-1183

Why Your Website Shows a 'Your Connection Is Not Private' Error and How to Fix It

Summary

This guide helps you troubleshoot and resolve: Why Your Website Shows a 'Your Connection Is Not Private' Error and How to Fix It. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

When visitors try to access your website and see a warning that their connection is not private, it usually means there is a problem with your site's SSL/TLS certificate. This certificate encrypts data between your website and your visitors' browsers. When it is missing, expired, or misconfigured, modern browsers such as Google Chrome, Microsoft Edge, and Apple Safari display a security warning to protect users. While this error can be alarming, most causes are straightforward to diagnose and resolve.

Before making any changes to your SSL configuration or .htaccess file, back up your website files and database. Incorrect changes can take your website offline.

Quick Fix Steps

  1. Refresh the page after waiting a few minutes to rule out a temporary connection glitch.
  2. Check that your website address begins with https:// rather than http://.
  3. Confirm your SSL certificate has not expired by viewing the certificate details in your browser.
  4. Clear your browser cache and try accessing the site in an incognito or private window.
  5. Check if the error appears on multiple devices and networks. If only one device sees the warning, the issue is likely local to that device rather than your server.
  6. Contact your hosting provider or domain registrar if the certificate appears expired or invalid.

Detailed Instructions

Check the SSL Certificate in Your Browser

  1. Open your website in Google Chrome, Microsoft Edge, or Apple Safari.
  2. Click the security icon to the left of the website address in the address bar.
  3. Select Connection is secure or Certificate, depending on your browser.
  4. Review the expiry date and the issuing certificate authority.
  5. If the date has passed, your certificate has expired and must be renewed.

Renew or Reinstall Your SSL Certificate

  1. Log in to your web hosting control panel or domain registrar account.
  2. Navigate to the SSL/TLS, Security, or Website Security section.
  3. Select your domain and choose the option to renew, reissue, or install a certificate.
  4. If you use Let's Encrypt via command line, run: certbot renew. If your hosting dashboard provides a button, click Renew.
  5. Save the changes and wait for the certificate to propagate, which can take up to an hour.

Force HTTPS via .htaccess

  1. Log in to your hosting control panel and open File Manager.
  2. Locate the .htaccess file in your public_html or root directory.
  3. Edit the file and add the following lines at the top:
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
  1. Save the file and test your website by visiting http://yourdomain.com.au. It should automatically redirect to https://.

Force HTTPS in WordPress

  1. Log in to your WordPress admin dashboard.
  2. Go to Settings > General.
  3. Update WordPress Address (URL) and Site Address (URL) to start with https://.
  4. Click Save Changes.
  5. Install a mixed content plugin such as Really Simple SSL or Better Search Replace to update internal links from http:// to https://.

Fix Mixed Content Warnings

  1. Open your website and press F12 to open Developer Tools.
  2. Click the Console tab.
  3. Look for warnings stating that insecure content (http://) is being loaded on a secure page.
  4. Update those links in your website files or content management system to use https://.
  5. Save your changes and refresh the website.

Clear Browser Cache and SSL State

  1. In Google Chrome or Microsoft Edge, press Ctrl + Shift + Delete.
  2. Select Cached images and files and click Clear data.
  3. In Apple Safari, go to Safari > Settings > Privacy > Manage Website Data > Remove All.
  4. Restart the browser and revisit your website.

Check Certificate Chain and Intermediate Certificates

If your certificate is installed but browsers still show a privacy error, the intermediate certificate may be missing. This creates an incomplete certificate chain.

  1. Use an online SSL checker such as SSL Shopper or Qualys SSL Labs to test your domain.
  2. Look for warnings about missing intermediate certificates or an incomplete chain.
  3. Log in to cPanel and go to Security > SSL/TLS Manager, or Plesk and go to Websites & Domains > SSL/TLS Certificates.
  4. Reinstall the certificate, ensuring you include the full certificate bundle (primary certificate plus intermediate/CA bundle).
  5. Save the changes and retest your domain with the SSL checker.

Certificate Issued for the Wrong Domain

Ensure the SSL certificate matches your exact domain name. A certificate for www.example.com.au may not cover example.com.au unless both are listed as subject alternative names. Reissue the certificate to include all variations of your domain.

Certificate Not Trusted

Self-signed certificates are not trusted by browsers and will trigger a privacy error. Use a certificate issued by a recognised certificate authority, or install a free trusted certificate through your hosting provider.

Server Date and Time Incorrect

If your web server's clock is incorrect, SSL certificates may appear invalid. Verify that your server is set to the correct time zone and that automatic time synchronisation is enabled.

Cloudflare SSL/TLS Configuration

If you use Cloudflare, a mismatch between Cloudflare's SSL mode and your origin server's configuration can cause privacy errors.

  1. Log in to your Cloudflare dashboard.
  2. Select your domain and go to SSL/TLS > Overview.
  3. Review the encryption mode:
  1. Ensure the mode matches your origin server setup. If you have an SSL certificate installed on your server, use Full or Full Strict.
  2. Go to SSL/TLS > Edge Certificates and ensure Always Use HTTPS is enabled.
  3. If you recently enabled HSTS, check the HSTS preload settings. Removing a domain from the HSTS preload list can take time, so plan changes carefully.

If you recently moved your website to a new host, remember that DNS changes can take up to 48 hours to propagate globally. During this time, some visitors may see security warnings until the new SSL certificate is fully recognised.

Avoid bypassing the privacy warning on a live business website. Visitors who click through the warning may expose sensitive data, and the warning will damage trust in your organisation.

If you have checked your certificate expiry, renewed the SSL, cleared your browser cache, and verified your certificate chain but the error persists, Open a Ticket with your hosting provider for further assistance.

If you host with us, you don't need to do this yourself — just Open a Ticket and our Brisbane team will get it sorted.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket