Skip to content
Websites & web security

How to Fix an Expired SSL Certificate – Quick Guide for Website Owners

Learn why your site shows “Not secure”, how to renew an expired SSL certificate, and restore visitor trust with step‑by‑step instructions and a handy checklist.

Business owner reviewing website security warning on laptop
Illustration generated with AI.

When visitors see a “Not secure” badge because your SSL certificate has expired, they often leave the site, hurting traffic and trust.

The quickest fix is to obtain a new certificate, install it on your server, and confirm the change – all of which we explain below.

Why an expired SSL certificate shows ‘Not secure’

SSL/TLS encrypts every request between browser and server

When a visitor opens a site that uses HTTPS, the browser initiates an SSL/TLS handshake. During this handshake the server presents a digital certificate that contains its public key, the domain name, and a validity period defined by a start and an expiry date. The browser checks the certificate against trusted root authorities and verifies that the current date falls inside the validity window. If the check succeeds, the browser creates a symmetric session key, encrypts all subsequent HTTP traffic, and displays the padlock icon.

What happens when the certificate date is past

Once the expiry date is reached, the certificate is no longer considered trustworthy. The browser cannot confirm that the site is still owned by the same entity, and it cannot guarantee that the encrypted channel is safe from man‑in‑the‑middle attacks. As a result, browsers on both Windows and Linux platforms interrupt the connection and show a “Not secure” warning, often accompanied by a red strike‑through on the URL bar. The warning appears regardless of the operating system because the validation logic is built into the browser itself, not the host OS.

Why the warning matters for Qubitpage‑hosted sites

Qubitpage builds websites, online stores and custom platforms on its CarphaCom stack (Next.js + MedusaJS) and hosts them on VPS instances located in EU data centres. Those servers run Linux, while many of Qubitpage’s clients manage their sites from Windows workstations. An expired certificate therefore triggers the same “Not secure” message for every visitor, whether they are using Chrome on Windows, Firefox on Linux, or any other modern browser. The message reduces user confidence, can lower conversion rates for e‑commerce stores, and may even affect search‑engine rankings.

Technical signals that the certificate has expired

Browsers display a specific error code (e.g., NET::ERR_CERT_DATE_INVALID in Chrome) and show the exact date range of the certificate. The same information can be retrieved with command‑line tools such as openssl s_client -connect example.com:443 -servername example.com on Linux or PowerShell’s Invoke-WebRequest on Windows. Both commands return the certificate’s “Not After” field, confirming that the date is in the past.

Understanding why the warning appears is the first step toward fixing it. After confirming the expiry, the next sections will guide you through checking the current status, renewing the certificate, and updating server configuration. For a quick assessment of your site’s health, you can also request a free website check from Qubitpage at /contact.

How to check the current certificate status

Browser lock icon

Open the website in any modern browser and look at the address bar. A closed padlock indicates a valid certificate, while an open padlock or a warning triangle means the certificate is expired or mis‑configured. Click the padlock to open the certificate details; most browsers show the “Valid from” and “Valid until” dates directly. If the “Valid until” date is in the past, the SSL certificate has expired.

Online SSL checker

Several free tools inspect a site’s TLS configuration without installing software. Navigate to a service such as SSL Labs or SSL Shopper, enter the domain name, and start the test. The results page lists the certificate chain, expiration date, and any errors detected. Look for a status like “Certificate has expired” or a red warning flag. These tools also reveal whether intermediate certificates are missing, which can cause the same “Not secure” warning even when the leaf certificate is still valid.

Command‑line OpenSSL test

For developers or system administrators who prefer the terminal, the OpenSSL utility provides a quick verification command. Run:

openssl s_client -connect example.com:443 -servername example.com 

After the handshake completes, press Ctrl‑C to stop the output. Scroll to the section that begins with Certificate chain and locate the line notAfter=. The date shown is the certificate’s expiration. If the date is earlier than today, the certificate is expired.

To extract only the expiration date, pipe the output through openssl x509 like this:

echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -dates

When to involve Qubitpage managed hosting

If your site runs on a VPS or shared server that you manage yourself, you must install and renew certificates manually. Qubitpage’s managed hosting plans include automatic SSL provisioning and renewal via Let’s Encrypt, removing the need for manual checks. The Business plan even covers daily AI‑generated content, while the Shop plan adds e‑commerce‑ready SSL without extra configuration.

Tip: After confirming an expired certificate, clear your browser cache before re‑checking. Cached SSL information can display outdated warnings even after a successful renewal.

Steps to renew or replace an expired SSL certificate

  1. Choose a Certificate Authority (CA) that fits your budget and validation level. Popular options include Let’s Encrypt for free domain‑validated certificates or commercial CAs such as DigiCert for extended validation.

  2. Generate a Certificate Signing Request (CSR) on the server that hosts your site. On a typical Linux box run:
    openssl req -new -newkey rsa:2048 -nodes -keyout example.key -out example.csr
    Provide the fully qualified domain name (FQDN) when prompted.

  3. Submit the CSR to the chosen CA through its web portal. The CA will verify domain ownership (via email, DNS TXT record, or HTTP file) and then issue a certificate bundle containing the server certificate, intermediate chain, and root certificate.

  4. Download the issued files and copy them to the appropriate directory on your server, for example /etc/ssl/example/. Ensure the private key (example.key) remains protected with permissions 600.

  5. Edit your web server configuration to reference the new files. For Nginx, update the ssl_certificate and ssl_certificate_key directives; for Apache, modify SSLCertificateFile and SSLCertificateKeyFile accordingly.

  6. Test the configuration syntax. Nginx: nginx -t; Apache: apachectl configtest. Resolve any errors before proceeding.

  7. Reload or restart the web service to apply the new certificate. Nginx: systemctl reload nginx; Apache: systemctl restart httpd. Verify the certificate is active with openssl s_client -connect yourdomain.com:443 -servername yourdomain.com or an online SSL checker.

  8. If you use Qubitpage’s managed hosting, the renewal can be automated. The Business plan (29 €/month) includes automatic SSL renewal and installation, removing the need for manual CSR generation. Contact support to enable the feature on your VPS.

Updating DNS and server configuration after renewal

Confirm virtual‑host definitions

After the new certificate is installed, open each virtual‑host file that serves the domain. On Linux systems these files are typically located in /etc/nginx/sites‑available or /etc/apache2/sites‑enabled. Verify that the server_name (or ServerName) matches the domain you just renewed. If the host definition points to an old alias, update it to the current domain name and save the file.

On Windows servers that run the Carpathron Remote service, the equivalent configuration resides in the IIS site bindings. Open the IIS Manager, select the site, and ensure the binding lists the renewed domain under “Host name”. This step mirrors the Linux virtual‑host verification and prevents the server from serving a stale certificate.

Replace hard‑coded certificate paths

Search the virtual‑host configuration for the certificate file directives. In Nginx this is the ssl_certificate and ssl_certificate_key lines; in Apache it is SSLCertificateFile and SSLCertificateKeyFile. Replace any absolute paths that still reference the previous certificate files with the paths of the newly generated .crt and .key files. On Windows/IIS, use the “SSL Settings” dialog to browse to the new certificate store entry instead of a file path.

If you deployed the certificate via a management tool such as Certbot, the tool often creates symbolic links like live/example.com/fullchain.pem. Ensure those links point to the latest files; otherwise update the links or edit the configuration to reference the explicit files.

Reload or restart the web server

Once the configuration files contain the correct paths, reload the web server to apply the changes without dropping existing connections. For Nginx run sudo systemctl reload nginx; for Apache use sudo systemctl reload apache2. A full restart (sudo systemctl restart …) is also acceptable if you prefer to clear all worker processes.

On a Windows host running Carpathron Remote, open a PowerShell prompt and execute iisreset /restart or use the “Restart” button in IIS Manager. This action forces IIS to read the updated certificate binding and serve the renewed certificate to clients.

Tip: After reloading, clear your browser cache or use an incognito window to verify that the new certificate is presented; cached SSL sessions can show the old expiration date.

Validate the final setup

Run an external SSL test such as Qualys SSL Labs to confirm the server now presents the renewed certificate chain and that no mixed‑content warnings appear. Additionally, check the DNS records for the domain to ensure they still point to the correct IP address; the renewal process does not modify DNS, but a mis‑typed A or CNAME record can cause the request to reach a different server that still hosts the expired certificate.

If the test reports a mismatch, revisit the virtual‑host files and the IIS bindings, correct any lingering references, reload the server again, and repeat the validation step. Once the test returns a “Grade A” or higher, the SSL renewal is complete and the site will be trusted by visitors.

SSL renewal checklist

Before you start the renewal process, confirm that you have access to the domain registrar account and the server where the current certificate is installed. Verify that the CSR (Certificate Signing Request) matches the domain list and that you have a backup of the existing certificate files in case you need to revert.

During renewal, generate a new CSR if required, submit the request to your CA (Certificate Authority), and download the issued certificate bundle. Install the new certificate and intermediate chain on the web server, then restart the relevant services to load the updated files.

After the certificate is live, test the HTTPS connection with tools such as openssl s_client or an online SSL checker. Ensure that the certificate chain is complete, the expiration date reflects the new term, and that mixed‑content warnings are resolved on all pages.

Phase Item to verify How to verify
Before renewal Domain ownership and CSR validity Log into the registrar, confirm the domain points to your server; run openssl req -noout -text -in csr.pem to inspect the CSR
During renewal Certificate bundle completeness After downloading, concatenate the server cert and intermediate certs; use openssl verify -CAfile bundle.pem server.crt to check the chain
After renewal HTTPS response and mixed content Open the site in a browser, view the lock icon, and run curl -I https://yourdomain.com to see the new expiry date; scan pages for HTTP resources
Ongoing Monitoring and alerts Configure a monitoring service or use Qubitpage’s managed hosting plan (contact us) to receive email alerts 30 days before the next expiry

Document the renewal date, the CA used, and the private key location in a secure vault. Store the renewal receipt and the CA’s root certificate for future audits.

Finally, update any internal documentation or automation scripts that reference the old certificate fingerprint. Keeping this checklist up to date reduces downtime and ensures that visitors always see a valid “secure” lock icon.

Preventing future expirations with automated tools

Automatic renewal eliminates the risk of a certificate lapsing while you focus on content and conversions. Below are three practical mechanisms that keep the HTTPS lock active without manual intervention.

Let’s Encrypt auto‑renewal

Let’s Encrypt issues free certificates that are valid for 90 days. Most web servers support a built‑in renewal script that runs daily via cron. To enable it, install the certbot client, run certbot --nginx (or --apache), and confirm that the line 0 0 * * * certbot renew --quiet appears in /etc/crontab. The script checks the expiration date, contacts the Let’s Encrypt CA, and installs the new certificate automatically.

Qubitpage managed hosting auto‑renew feature

When a site is hosted on Qubitpage’s managed platform, the SSL certificate is tied to the hosting plan. The Business, Shop and Platform tiers include an auto‑renew service that renews the certificate before it expires and updates the server configuration silently. To activate it, simply select the appropriate plan during the checkout at Website Services. Qubitpage handles the renewal on the VPS in an EU data centre, preserving the existing DNS records and keeping the site online.

Calendar reminders and manual checks

Even with automation, a secondary reminder can catch unexpected failures. Create a recurring event in your preferred calendar (Google Calendar, Outlook, etc.) that triggers 30 days before the next renewal date. Include the link to the free website check service (contact@qubitpage.com) so you can verify that the certificate is active after each renewal cycle.

Combining an automated renewal method with a simple calendar alert provides a safety net that virtually guarantees continuous HTTPS protection. Use the free website check to confirm the lock icon appears in the browser and to receive a fixed quote for any additional services you might need.

Frequently asked questions

How can I tell if my SSL certificate is really expired and not just mis‑configured?

Use an online SSL checker or run openssl s_client -connect yourdomain.com:443 -servername yourdomain.com and look for the Not After date in the output. If the date is past, the certificate is expired; if the date is current but browsers still show a warning, verify that the certificate chain includes the intermediate certificates.

Do I need to buy a new certificate or can I reuse the old one after renewal?

Most Certificate Authorities allow you to renew the existing certificate using the same private key and CSR, which keeps the same domain validation status. You only need to purchase a renewal if the CA’s policy requires a new issuance; otherwise, the renewal process updates the expiration date without changing the underlying certificate.

What is the difference between renewing on a Linux server and a Windows server?

On Linux you typically replace the .crt and .key files and reload the web server (e.g., systemctl reload nginx or apachectl graceful). On Windows you use the IIS Manager to import the new certificate, bind it to the site, and then restart the site or the IIS service.

Will renewing the certificate affect my SEO ranking?

Search engines treat a valid HTTPS connection as a ranking signal, so an expired certificate can cause a temporary dip in rankings. Once the renewed certificate is installed and the site serves a valid HTTPS response, the ranking impact disappears within a few days as crawlers re‑index the site.

Can Qubitpage handle SSL renewal for my site automatically?

Qubitpage offers managed hosting on EU‑based VPSes with daily backups, DDoS protection and monitoring. As part of the Business and Shop plans, SSL certificates are maintained and renewed automatically, ensuring continuous HTTPS coverage without manual intervention.

Final steps and next actions

After renewing the certificate on your server, reload the web service to apply the new file and verify the chain with openssl s_client -connect yourdomain.com:443 -servername yourdomain.com. Check the browser lock icon on multiple devices to confirm the warning has disappeared.

Update any monitoring tools or uptime checks to use the new expiration date, and schedule a reminder a month before the next renewal. If you host the site on a VPS, consider enabling Qubitpage’s managed hosting plan, which includes daily backups, SSL management and DDoS protection, so future renewals are handled automatically.

Should you encounter configuration issues or need a fresh setup, Qubitpage can rebuild the site on the CarphaCom platform with a fully responsive design and built‑in SSL. Explore our website services to keep your online presence secure and running smoothly.

Written by

Mircea S. Rusu

Founder and engineer of Qubitpage. Support engineer since 2005, CMS developer, former technical consultant at Niguarda Ca' Granda Hospital in Milan, and author of the book “The Architect”.

More about the author →