Home › Knowledgebase › KB-1298

How to fix ssl certificate error on my website

Summary

This guide helps you troubleshoot and resolve: How to fix ssl certificate error on my website. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

An SSL certificate error means your website's secure connection cannot be verified by a visitor's web browser. When this happens, browsers such as Google Chrome, Microsoft Edge, or Apple Safari display warnings like "Your connection is not private" or "Not secure," which can deter customers and harm your online reputation. For Australian small businesses, a secure site is essential for protecting customer data, maintaining trust, and supporting search engine optimisation (SEO), as Google uses HTTPS as a ranking signal.

Remember — 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.

Quick Fix Steps

  1. Check whether your SSL certificate has expired.
  2. Confirm that your website is forcing HTTPS instead of loading over HTTP.
  3. Look for mixed-content warnings where some page elements load over an insecure connection.
  4. Clear your browser cache or test in an incognito window to rule out local caching issues.
  5. Check your CDN SSL settings, such as Cloudflare, to ensure the encryption mode is set correctly.
  6. If the problem persists, Open a Ticket for assistance.

Detailed Instructions

Check certificate expiry

  1. Open your website in Google Chrome or Microsoft Edge.
  2. Click the padlock icon in the address bar to view the connection security information.
  3. Click "Connection is secure" or "Certificate is valid" to view the certificate details.
  4. Check the expiry date. If the date has passed, the certificate needs to be renewed.
  5. To identify your certificate issuer, look at the "Issued by" field in the certificate details window. Renew the certificate through that provider or your hosting control panel.

Verify certificate chain and intermediate certificates

  1. Open your website in Google Chrome and click the padlock icon in the address bar.
  2. View the certificate details and navigate to the certification path or chain tab.
  3. Ensure the chain includes the root certificate, any intermediate certificates, and your domain certificate.
  4. If an intermediate certificate is missing, download the correct chain file from your certificate authority.
  5. Install the intermediate certificate on your server. In cPanel, go to Security > SSL/TLS Status, select your domain, and click Manage SSL sites to paste the certificate bundle (CRT) including the intermediate certificate. In Plesk, go to Websites & Domains > Hosting Settings > SSL/TLS certificates and upload the full certificate chain.

Force HTTPS redirects

  1. Log in to your website's hosting control panel or content management system.
  2. In cPanel, navigate to Domains > Force HTTPS Redirect and toggle the switch to On for your domain.
  3. In Plesk, go to Websites & Domains > Hosting Settings, select SSL/TLS support, and enable Permanent SEO-safe 301 redirect from HTTP to HTTPS.
  4. If you use WordPress, install the Really Simple SSL plugin, go to Settings > SSL, and click Activate SSL.
  5. Save your changes and test the website by typing http://yourdomain.com.au in the address bar. It should automatically load as https://yourdomain.com.au.

Fix mixed-content errors

Before performing any search-and-replace operations on your website files or database, create a full backup of your website files and database. Incorrect replacements can break your site.
  1. Open your website in Google Chrome and press F12 to open Developer Tools.
  2. Click the Console tab and look for warnings labelled "Mixed Content." These indicate images, scripts, or stylesheets loading over http:// instead of https://.
  3. Edit your website's files or database to replace http:// URLs with https://. If you use WordPress, a search-and-replace plugin can help update internal links safely.
  4. Save the changes and refresh the page to confirm the warnings disappear.

Check CDN and Cloudflare SSL settings

  1. Log in to your CDN provider, such as Cloudflare.
  2. Select your domain and navigate to the SSL/TLS app.
  3. Review the encryption mode setting. Flexible encrypts traffic between the visitor and Cloudflare but not between Cloudflare and your origin server, which can cause redirect loops or insecure warnings. Full or Strict encrypts traffic both ways.
  4. If your origin server has a valid SSL certificate, change the mode to Full or Strict. If you select Strict, ensure your origin certificate is valid and trusted.
  5. Purge the cache after changing SSL settings to ensure visitors receive the updated configuration.

Renew an SSL certificate

  1. Identify your certificate issuer by clicking the padlock icon in your browser and viewing the certificate details under "Issued by."
  2. If your certificate was issued by your hosting provider, log in to your control panel. In cPanel, go to Security > SSL/TLS Status and select Run AutoSSL to renew free certificates. For paid certificates, go to SSL/TLS Manager to generate a new CSR and install the renewed certificate.
  3. In Plesk, go to Websites & Domains > SSL/TLS certificates, select the expiring certificate, and click Renew or upload the new certificate files provided by your certificate authority.
  4. If you do not know your certificate authority, check the invoice or welcome email from when the certificate was purchased, or contact your previous website administrator.
  5. After installation, restart your web server if required and test the site in an incognito window.

Troubleshooting

Certificate not trusted

If visitors see a warning that the certificate is not trusted, it may be self-signed or issued by an authority the browser does not recognise. Install a certificate from a trusted certificate authority, or reissue your existing certificate through your hosting provider.

Incorrect domain name on certificate

An SSL certificate must match the exact domain name used to access the site. If your certificate covers www.example.com.au but visitors go to example.com.au, they may see a mismatch error. Ensure the certificate includes both the www and non-www versions of your domain.

Server configuration issues

Outdated server software or incorrect TLS settings can cause connection failures. Confirm your web server supports modern TLS versions (TLS 1.2 or higher) and that the certificate chain, including any intermediate certificates, is installed correctly.

Self-managed servers

If you manage your own server without a hosting control panel, you will need to install the certificate manually using your web server software. For Apache, update the SSLCertificateFile, SSLCertificateKeyFile, and SSLCertificateChainFile directives in your virtual host configuration. For Nginx, combine the domain certificate and intermediate certificate into a single bundle file and reference it in the ssl_certificate directive. After making changes, run a configuration test and reload the web server service.

Why HTTPS matters

Do not ignore persistent SSL errors. Visitors may be blocked from accessing your site entirely, and prolonged security warnings can negatively affect your search engine visibility and customer trust.
Remember — 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