How to Install and Renew an SSL Certificate: HTTPS Setup and Troubleshooting Guide
SSL certificatesHTTPSTLSwebsite securitymixed contenthosting panels

How to Install and Renew an SSL Certificate: HTTPS Setup and Troubleshooting Guide

WWebhost.link Editorial Team
2026-11-19
7 min read

A practical SSL checklist for installing certificates, forcing HTTPS, fixing mixed content, verifying renewals, and troubleshooting browser warnings.

Installing an SSL certificate is only one part of moving a website to HTTPS. This reusable checklist covers certificate selection, hosting-panel installation, automatic renewal, HTTP-to-HTTPS redirects, canonical URLs, subdomains, mixed-content cleanup, and the checks that help you recover from certificate errors without taking unnecessary risks.

Overview

HTTPS encrypts the connection between a visitor’s browser and your website. It also allows the browser to verify that the certificate presented by the server matches the domain being visited. A correct HTTPS setup therefore depends on more than uploading certificate files: the domain must resolve to the intended server, the certificate must cover the right hostname, the server must be configured to use it, and the site must consistently load secure resources.

Many hosting providers can issue and install a certificate automatically, often through the hosting control panel. Other setups require you to create a certificate signing request, obtain certificate files from a certificate authority, and install the certificate, private key, and any required intermediate chain manually. The exact labels differ between cPanel, custom dashboards, managed WordPress platforms, VPS control panels, and command-line configurations, but the verification workflow is broadly the same.

Before making changes, record the current configuration and confirm that you have access to the hosting account, domain registrar, DNS provider, CMS administrator account, and any server or deployment tools involved. If the site is business-critical, test the change in a staging environment first. The website staging environment guide explains how to test hosting changes before publishing them.

Checklist by scenario

For a new website

  1. Confirm the hostnames. List every hostname the site will use, such as the preferred domain, the www version, a separate admin hostname, and any planned subdomains. A certificate for one hostname may not cover another.
  2. Point DNS to the correct destination. Check the A, AAAA, or CNAME records that direct traffic to the host. If DNS is still changing, certificate issuance may fail or may validate the wrong server. Use the DNS troubleshooting guide when records or nameservers are unclear.
  3. Enable the certificate. In the hosting panel, look for SSL, TLS, Security, or Let’s Encrypt settings. Choose automatic issuance when it is supported and verify that both the main hostname and required aliases are included.
  4. Test HTTPS before redirecting. Open the HTTPS address directly and inspect the certificate details in the browser. Confirm the hostname, validity period, and issuing authority, and check that the page loads without a certificate warning.
  5. Set the preferred URL. Decide whether the site uses www or the non-www version, then redirect the alternate hostname to it. Update the CMS site URL, canonical URL, sitemap, and internal links to use the preferred HTTPS address.

For an existing HTTP website

  1. Back up before editing. Save the site files, database, server configuration, and current redirect rules. Keep a copy of the previous configuration so you can roll back if a redirect loop or application error appears.
  2. Install and test the certificate first. Do not begin with a blanket redirect. Visit the HTTPS version directly, test representative pages, submit forms, sign in, and check media, scripts, stylesheets, and web fonts.
  3. Update application settings. In WordPress or another CMS, change the site and home URLs to HTTPS using the platform’s settings or a carefully tested migration tool. Update hard-coded HTTP references in templates, databases, configuration files, and content where necessary.
  4. Force HTTPS at the server or hosting layer. Enable the host’s redirect option or add a suitable HTTP-to-HTTPS rule in the appropriate configuration file. Use a permanent redirect for the final migration, but test the rule carefully to avoid loops.
  5. Check search and analytics settings. Update property, sitemap, callback, webhook, and monitoring URLs where HTTPS changes the address. Keep redirects from old HTTP URLs so existing links can continue to reach the secure version.

For a renewal or replacement

  1. Check the certificate’s expiration date and identify whether renewal is handled by the hosting provider, a certificate management system, or a manual process.
  2. Confirm that automatic renewal can complete validation. HTTP-based validation may require a reachable validation path, while DNS-based validation may require an unchanged TXT record or API access.
  3. Make sure the renewal covers the same hostnames as the existing certificate. A new certificate can be valid while still omitting a recently added subdomain.
  4. After renewal, inspect the certificate served by the live site rather than relying only on the hosting dashboard. Clear caches or reload the service if the provider’s instructions require it.
  5. Record the renewal method, responsible account, validation records, and notification address. This makes the next renewal easier to audit.

For a subdomain or migrated site

Treat every subdomain as a separate HTTPS endpoint unless your certificate and hosting setup explicitly cover it. Check DNS, virtual-host configuration, application URLs, cookies, redirects, and certificate coverage together. During a migration, install the certificate on the new server before changing traffic, then test the new destination using a temporary hostname or local verification method where practical. The website migration checklist provides a broader sequence for moving a site without overlooking DNS and rollback steps.

What to double-check

Use this verification list after installation, renewal, DNS changes, or a hosting move:

  • The certificate is trusted by current browsers and matches the exact hostname in the address bar.
  • The certificate chain is complete, especially when the certificate was installed manually.
  • The private key belongs to the certificate and is stored with restricted access.
  • The server supports modern TLS settings supplied or recommended by the hosting platform. Avoid changing protocol or cipher settings without understanding the compatibility impact.
  • HTTP requests redirect once to the correct HTTPS URL, with no repeated redirects between www and non-www versions.
  • Images, stylesheets, JavaScript, fonts, videos, API calls, embedded content, and form actions all use HTTPS or a compatible secure URL.
  • The canonical tag, XML sitemap, robots directives, structured data, hreflang references, and internal links use the preferred HTTPS version.
  • Login sessions, cookies, payment flows, webhooks, email links, and third-party integrations still work.
  • Monitoring checks both the certificate expiration date and the ability to complete a normal HTTPS request.

Mixed content occurs when an HTTPS page requests a resource over HTTP. Browsers may block active content such as scripts and frames, or warn about passive content such as images. Open the browser’s developer tools, review the Console and Network panels, identify the insecure URL, and correct it at the source. Search the database or deployment files for hard-coded HTTP references when the problem appears across many pages.

Common mistakes

  • Installing a certificate for the wrong hostname: The certificate may cover example.com but not www.example.com or shop.example.com. Verify each hostname before changing redirects.
  • Redirecting before HTTPS works: A redirect cannot repair an invalid certificate. Test the destination directly first, or visitors may be sent from a reachable HTTP page to an inaccessible HTTPS page.
  • Creating a redirect loop: This often happens when the server redirects to HTTPS while a proxy or CMS reports that the original request was HTTP. Review proxy settings and trusted forwarded-protocol headers.
  • Forgetting renewal ownership: Automatic renewal can fail when DNS validation records are deleted, domain access changes, or the certificate account is no longer monitored. Keep renewal alerts directed to a maintained address.
  • Changing DNS records casually: A certificate issue may appear to be a web-server problem when the domain still points to an old host. For mail-related records, consult the guide to SPF, DKIM, DMARC, and MX records before editing DNS.
  • Using a broad search-and-replace without a backup: Database URL replacements can damage serialized application data or alter unrelated values. Use platform-aware tools and test the result.

If the browser reports that the certificate has expired, first check the server time and the certificate actually being served. If it reports a name mismatch, inspect the hostname and certificate coverage. If it reports an untrusted issuer or incomplete chain, reinstall the correct chain supplied by the certificate provider. If the error appears only on one network, compare DNS responses and proxy or firewall behavior before changing the certificate.

When to revisit

Revisit this checklist before a certificate’s renewal window, when launching a new hostname or subdomain, after changing nameservers or DNS records, during a hosting migration, and after changing a reverse proxy, CDN, web server, or CMS URL configuration. It is also worth reviewing after an outage, a browser certificate warning, a failed deployment, or the addition of a new third-party integration.

At each review, confirm who owns the domain and hosting accounts, where renewal alerts are delivered, which system performs renewal, and how the team would roll back a faulty redirect or server change. Keep a dated record of the certificate coverage, preferred canonical URL, redirect location, and test results. For broader domain ownership and renewal checks, use the domain portfolio audit template.

Finish with a practical live test: open the preferred HTTPS URL in a private browser window, test an old HTTP URL, check one form or login flow, inspect the certificate details, and review the browser console for mixed-content errors. If all five checks pass and monitoring is configured, document the change and schedule the next renewal review rather than assuming the setup will remain correct indefinitely.

Related Topics

#SSL certificates#HTTPS#TLS#website security#mixed content#hosting panels
W

Webhost.link 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.