How to Renew and Troubleshoot SSL Certificates on Web Hosting
SSL certificatesHTTPSTLScertificate renewalcPanelwebsite security

How to Renew and Troubleshoot SSL Certificates on Web Hosting

WWebhosting.live Editorial Team
2026-11-19
8 min read

Use this checklist to renew SSL certificates, fix HTTPS errors, test redirects and mixed content, and hand off incidents without unnecessary downtime.

Renewing an SSL certificate should be a controlled maintenance task, not an emergency. This checklist explains how to renew automatic and manually managed certificates, install the replacement safely, resolve validation and browser errors, test HTTPS and redirects, and prepare a rollback or incident handoff if the site is already failing.

Overview

An SSL certificate enables a website to use HTTPS and helps browsers establish an encrypted connection. In practice, a certificate problem can come from several different layers: the certificate may be expired, issued for the wrong hostname, missing an intermediate certificate, unable to renew because DNS changed, or correctly installed while the website still loads insecure resources.

The exact menu names vary between hosting providers. A cPanel account may show SSL/TLS Status, AutoSSL, or Manage SSL Hosts, while a managed WordPress host or cloud platform may expose certificate controls in a custom dashboard. The underlying workflow is similar:

  1. Identify which hostname is failing and which certificate currently serves it.
  2. Confirm whether renewal is automatic or requires manual action.
  3. Resolve domain validation, DNS, or account issues before issuing a replacement.
  4. Install the certificate with its private key and required certificate chain.
  5. Test HTTPS, redirects, assets, applications, and alternate hostnames.
  6. Record the result and monitor the site after the change.

Before changing anything, create or verify a current backup and confirm that you have access to the hosting panel, DNS provider, certificate account, and any administrator email addresses used for validation. If the website is already unavailable, first determine whether the cause is the certificate, the web server, DNS, or the application. The guidance in How to Read Web Hosting Access and Error Logs can help separate those causes.

Checklist by scenario

Scenario 1: Automatic renewal is enabled

Automatic certificate systems generally attempt renewal before the existing certificate expires, but an enabled setting is not proof that the latest renewal succeeded. Use this checklist:

  • Open the hosting or certificate dashboard and confirm the certificate covers every required hostname, such as the root domain and the selected www or subdomain version.
  • Check the certificate’s expiration date, issuer, status, and most recent renewal attempt.
  • Confirm that the domain still points to the server expected by the certificate system.
  • Check whether DNS records, a CDN, proxy, firewall, or load balancer are answering validation requests instead of the hosting server.
  • Review the hosting panel’s AutoSSL, certificate, or renewal log for a specific validation error.
  • Run a renewal or recheck action only if the provider supports it and the domain is ready for validation.
  • After a successful renewal, test the public site from a private browser window and from a second network if practical.

Do not assume that renewing the certificate automatically fixes an incorrect redirect, mixed content, or an outdated certificate on a separate server. If the domain uses multiple servers, verify which endpoint each hostname reaches.

Scenario 2: A cPanel or similar panel manages the certificate

For a typical cPanel SSL certificate renewal, the labels may differ by host, but the sequence is usually:

  1. Open SSL/TLS Status or the provider’s certificate-management area.
  2. Identify domains with an expired, invalid, or soon-to-expire status.
  3. Run the panel’s AutoSSL check if automatic issuance is included with the account.
  4. Read the result for each domain rather than relying only on a green or red summary.
  5. Correct failed validation, DNS, or document-root issues and rerun the check.
  6. Use Manage SSL Sites, or the equivalent screen, to confirm that the new certificate is assigned to the correct virtual host.
  7. Verify that the certificate, private key, and certificate authority bundle match when the panel requires those fields separately.

Some hosting plans include automatic certificates; others require a paid commercial certificate or separate installation. Confirm the provider’s current renewal window, supported certificate types, validation methods, and any fees before replacing a certificate.

Scenario 3: Manual renewal with a commercial or externally issued certificate

Manual renewal normally involves ordering or renewing the certificate with the certificate provider, completing domain control validation, downloading the renewed certificate files, and installing them on the server. Validation may use a DNS record, an HTTP file, or an approval email, depending on the certificate and provider. Follow the provider’s current instructions because supported methods can change.

  1. Generate a certificate signing request (CSR) on the server or in the provider’s dashboard. Keep the private key private and backed up securely.
  2. Ensure the CSR names the correct domain and includes required subject alternative names.
  3. Complete the selected validation method without changing unrelated DNS or website configuration.
  4. Download the issued certificate and any required intermediate or chain file.
  5. Install the certificate, private key, and chain in the hosting panel or web server configuration.
  6. Reload or restart the relevant service only after checking the configuration for errors.
  7. Test the live endpoint and confirm that the old certificate is no longer being served.

If the site runs on more than one web server, CDN, reverse proxy, or load balancer, install the replacement everywhere that terminates TLS. A certificate installed on the origin server will not necessarily change what visitors see if another service handles HTTPS first.

Scenario 4: The certificate has expired or browsers show a warning

Do not start by deleting the old certificate. First capture the browser error, affected hostname, server address, and current certificate details. Then:

  • Check whether the system clock on the client or server is correct.
  • Confirm that the certificate is expired, not merely issued for a different hostname.
  • Check DNS and validation records before requesting a replacement.
  • Renew or issue the replacement certificate through the current provider.
  • Install it on the endpoint that visitors actually reach.
  • Test from an external connection after DNS or CDN changes have had time to take effect.

If renewal cannot be completed immediately, avoid telling visitors to bypass the warning. Use a maintenance response only when necessary, and prioritize restoring a valid certificate and checking for unauthorized configuration changes.

What to double-check after renewal

CheckWhat to confirm
Hostname coverageThe certificate matches every public hostname in use, including the intended www and subdomain versions.
Expiration and issuerThe live endpoint serves the new certificate with the expected validity period and issuer.
Certificate chainRequired intermediate certificates are installed so common browsers and clients can build a trusted chain.
HTTPS redirectHTTP requests redirect to the intended HTTPS URL without loops or unexpected hostname changes.
Mixed contentImages, scripts, stylesheets, fonts, forms, and API calls load over HTTPS or are updated to secure URLs.
Application behaviorLogin, checkout, webhooks, APIs, cookies, and third-party integrations still work.
Alternate endpointsCDNs, staging exclusions, IPv4 and IPv6 endpoints, and additional servers are not serving an old certificate.

Mixed-content warnings are not usually fixed by issuing another certificate. Search the application configuration, database content, theme, plugins, and hard-coded links for http:// references. Update canonical URLs and trusted proxy settings carefully, especially on WordPress or applications behind a CDN. If a configuration change also affects PHP or application compatibility, use a test and rollback process such as the one described in How to Upgrade PHP on Web Hosting Safely.

After testing, document the certificate owner, renewal method, domains covered, validation method, hosting endpoint, expiration date, and next review date. Store private keys and backup files securely; do not paste them into tickets, chat messages, or public repositories.

Common mistakes

  • Waiting for the expiration day: A failed validation, DNS change, or support delay can turn routine maintenance into downtime. Review the renewal status in advance.
  • Renewing the wrong hostname: A certificate for the root domain does not automatically cover every subdomain. Compare the certificate names with the actual URLs visitors use.
  • Installing only the leaf certificate: Some clients need the intermediate chain as well. Use the provider’s recommended bundle and verify the live chain.
  • Changing DNS without recording the previous state: Save the existing records and change only what validation requires.
  • Testing only one URL: Check HTTP and HTTPS, www and non-www where relevant, key pages, forms, APIs, and any CDN endpoint.
  • Deleting the old certificate too soon: Keep a documented rollback path until the replacement is confirmed across all endpoints.
  • Ignoring the hosting layer: A provider may limit certificate types, automation, server access, or renewal actions. Confirm the plan’s capabilities before choosing a manual workflow.

For a broader security review after restoring HTTPS, use the Web Hosting Security Checklist. If the certificate issue appeared during a host move, compare the DNS and endpoint sequence with the website migration checklist.

Incident handoff template

When another administrator or hosting support team must take over, provide a concise handoff:

  • Incident: hostname, first observed time, and browser or client error.
  • Scope: affected URLs, regions, networks, applications, and whether HTTP is also affected.
  • Certificate state: expiration date, issuer, served hostname, and whether the chain is complete.
  • Validation state: automatic or manual renewal, validation method, last attempt, and exact failure message.
  • Changes made: DNS, hosting panel, web server, CDN, redirect, or application changes, with timestamps.
  • Evidence: safe screenshots, log excerpts, configuration versions, and test results. Exclude private keys and credentials.
  • Next action: named owner, rollback step, and the next verification time.

When to revisit

Review this checklist before each certificate renewal cycle and whenever you change domains, DNS, hosting, CDNs, load balancers, web servers, or validation contacts. Revisit it immediately after a browser reports a certificate warning, a migration changes the server endpoint, or an automatic renewal log shows a failure. Hosting panels, certificate authorities, supported validation methods, renewal windows, and provider fees can change, so verify those details against the current provider documentation rather than relying on an old screenshot or remembered menu path.

Keep a recurring calendar reminder well before the expiration date, but use the hosting dashboard and live certificate as the source of truth. Confirm that backups can be restored before making configuration changes; the guide to verifying and restoring web hosting backups provides a practical companion workflow. Once renewal is complete, record the result and schedule the next review. That small amount of documentation helps prevent a routine SSL task from becoming a website outage.

Related Topics

#SSL certificates#HTTPS#TLS#certificate renewal#cPanel#website security
W

Webhosting.live Editorial Team

Senior SEO Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.