Home › Knowledgebase › KB-1281

My website ssl certificate has expired how do i fix it

Summary

This guide helps you troubleshoot and resolve: My website ssl certificate has expired how do i fix it. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

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.

An SSL (Secure Sockets Layer) certificate encrypts the data exchanged between your website and its visitors. When a certificate expires, web browsers display security warnings that can deter customers and damage your organisation's credibility. Search engines also prioritise secure HTTPS sites, meaning an expired certificate can negatively impact your search rankings. This guide explains how to identify an expired certificate, renew it, and resolve common mixed-content warnings that appear after HTTPS is enabled.

Quick Fix Steps

  1. Verify that your SSL certificate has actually expired using an online SSL checker.
  2. Log in to your domain registrar or hosting control panel.
  3. Renew or reissue the SSL certificate for your domain.
  4. Install the new certificate on your web server.
  5. Force a HTTPS redirect to ensure all traffic uses the secure connection.
  6. Check your site for mixed-content errors and update any insecure asset links.
  7. Allow up to 24-48 hours for SSL changes to propagate globally before expecting the padlock to appear consistently.

Detailed Instructions

Step 1: Verify the certificate expiry date

  1. Open your website in Google Chrome, Microsoft Edge, or Apple Safari.
  2. Look for the warning icon in the address bar where the padlock usually appears.
  3. Click the warning icon and select Connection is not secure or Certificate invalid.
  4. View the certificate details and check the Valid to or Expiry date field.
  5. If the date has passed, your certificate has expired and must be renewed.

Step 2: Renew the SSL certificate

  1. Log in to your hosting control panel (for example, cPanel or Plesk) or the client area of your SSL certificate provider (such as Let's Encrypt, Comodo, or DigiCert).
  2. In cPanel, navigate to Security > SSL/TLS Status. In Plesk, navigate to Websites & Domains > SSL/TLS Certificates.
  3. Select the domain associated with the expired certificate.
  4. Click Renew, Reissue, or Generate Certificate.
  5. Complete the validation process, which may involve adding a DNS record or uploading a verification file to your web server.
  6. Download the issued certificate files, typically including the .crt certificate and .key private key.
Never share your private key (.key file) with anyone, including support staff, unless absolutely necessary and through a secure channel. Your private key must remain confidential to maintain the security of your encrypted connection. Do not email private keys or paste them into public ticket systems.

Step 3: Install the certificate on your server

  1. Return to your hosting control panel's SSL/TLS section.
  2. Choose the option to Install or Upload a certificate.
  3. Paste the certificate code into the Certificate field and the private key into the Private Key field.
  4. If provided, paste the CA Bundle or Intermediate Certificate into the relevant field.
  5. Click Install Certificate or Save.
  6. Restart your web server if required by your hosting environment.

Step 4: Enable HTTPS redirects

  1. Access your website's root directory via FTP or your hosting control panel's File Manager.
  2. Locate or create the .htaccess file if you are using an Apache server.
  3. Add the following redirect rule to force all traffic to HTTPS:
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
  1. Save the file and refresh your website to confirm the address bar now shows https://.
Incorrectly editing the .htaccess file can cause your website to display a 500 Internal Server Error. Always download a backup copy of the file before making changes.

Troubleshooting SSL Renewal Failures

If your certificate renewal fails, review the following common issues before contacting support.

DNS validation failures

If your provider uses DNS validation, ensure you have added the required TXT record to your domain's DNS zone exactly as provided. Common errors include missing underscores, trailing spaces, or incorrect record values. After adding the record, allow time for DNS propagation before attempting validation again.

CAA record issues

Certification Authority Authorisation (CAA) records specify which certificate authorities are permitted to issue certificates for your domain. If your DNS includes restrictive CAA records, renewal may fail. Check your DNS settings and ensure the CAA record allows your chosen provider (for example, Let's Encrypt, Comodo, or DigiCert) to issue certificates for your domain.

Propagation delays

After installing a renewed certificate or changing DNS records, changes can take up to 24-48 hours to propagate globally. During this period, some visitors may still see the old certificate or security warnings. Clear your browser cache and test from multiple networks before concluding the installation failed.

Troubleshooting Mixed-Content Warnings

After installing your SSL certificate, you may see a warning that your connection is "not fully secure" even though HTTPS is active. This happens when your page loads some assets—such as images, stylesheets, or scripts—over HTTP instead of HTTPS. This is known as mixed content.

How to identify mixed-content errors

  1. Open your website in Google Chrome.
  2. Press F12 or Ctrl + Shift + I to open Developer Tools.
  3. Click the Console tab.
  4. Look for warnings marked as Mixed Content that list insecure http:// URLs.

How to fix mixed-content errors

  1. Open the source code of the affected page or theme template.
  2. Find any hardcoded links starting with http:// for images, CSS, or JavaScript files.
  3. Change http:// to https://. Do not use protocol-relative URLs starting with //, as these are an anti-pattern and can cause loading issues.
  4. If you use a content management system like WordPress, go to Settings > General and ensure both the WordPress Address (URL) and Site Address (URL) start with https://.
  5. Save your changes and clear your website cache.
  6. Refresh the page and check the Developer Tools Console again to confirm the warnings are gone.

Preventing Future Expiry

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