Installing an SSL certificate is the step that enables HTTPS for a website, but a complete setup also requires correct DNS, server configuration, redirects, and testing. This reusable checklist explains how to install an SSL certificate on shared hosting, cPanel, WordPress, a VPS, or a custom server, then troubleshoot the most common HTTPS errors without overlooking email or subdomain settings.
Overview
An SSL certificate, commonly used as part of a TLS connection, allows a browser to establish an encrypted connection with your website. Once the certificate is correctly installed, visitors should be able to open the site at an https:// address and see a secure connection indicator in their browser.
Certificate installation is not the same as simply turning on HTTPS in a hosting dashboard. A reliable setup normally includes these stages:
- Confirm the domain and any required subdomains point to the correct server.
- Issue or obtain a certificate for every hostname that needs HTTPS.
- Install the certificate, private key, and certificate chain where required.
- Configure the web server to use HTTPS on the intended site.
- Redirect HTTP traffic to HTTPS after testing the secure version.
- Fix mixed content, application URLs, and canonical links.
- Verify renewal, redirects, certificates, and important site functions.
Before making changes, record your current configuration and create a backup of website files, databases, and relevant server settings. If you are comparing hosting options, the control panel and certificate workflow should be part of your evaluation. The guide to shared hosting, VPS, and cloud hosting can help clarify which level of server access your setup requires.
Checklist by scenario
Shared hosting or cPanel
Many shared hosting accounts provide an SSL area in the control panel. The exact label may vary, so look for terms such as SSL, TLS, certificates, or security.
- Confirm that the domain is added to the hosting account and resolves to the account’s server.
- Check that both the root domain and the www version are covered if both are used.
- Use the host’s certificate issuance or automatic certificate tool when available.
- If installing manually, enter the certificate, private key, and intermediate certificate chain in the matching fields.
- Assign the certificate to the correct domain or virtual host.
- Open the HTTPS version in a private browser window and test the site before enabling a permanent redirect.
Do not change DNS records casually if the domain also handles email or third-party services. For a refresher on this relationship, see DNS records explained.
WordPress
First install the certificate at the hosting or server level. Then update WordPress so its site address and WordPress address use HTTPS. In the WordPress dashboard, review the general URL settings and confirm that media, menus, forms, scripts, and plugins are not still requesting HTTP resources.
- Back up the database and files before changing site URLs.
- Update the WordPress and site URLs consistently.
- Clear caching at the WordPress, hosting, CDN, and browser levels.
- Search for hard-coded HTTP links in theme files, templates, database content, and custom scripts.
- Test login pages, forms, checkout pages, images, embedded content, and administrative screens.
HTTPS is one part of ongoing WordPress maintenance. Pair this work with the managed WordPress hosting maintenance checklist when reviewing updates, backups, and security settings.
VPS or custom Linux server
On a VPS, you usually control the web server configuration directly. Identify the active virtual host or server block, then obtain a certificate through your chosen certificate provider or certificate management tool. Store private keys with restricted permissions and keep them outside publicly served directories.
- Verify DNS resolution from the public internet before requesting the certificate.
- Confirm that the server can answer validation requests on the required hostname.
- Install the certificate and full chain in the web server configuration.
- Enable the HTTPS listener and reload the configuration after checking its syntax.
- Configure HTTP-to-HTTPS redirects for the intended site, while excluding any endpoint that genuinely requires HTTP.
- Schedule or verify renewal and test that the renewed certificate is deployed automatically or through a documented procedure.
After a migration or server rebuild, use a written hosting migration checklist so certificate files, DNS records, cron jobs, and application settings are not omitted.
CDN, proxy, or load balancer in front of the origin
HTTPS may terminate at the CDN or load balancer rather than at the origin server. Determine whether encryption is required only between visitors and the edge, or also between the edge and the origin. The origin must still be configured consistently with the proxy’s mode, hostname, and certificate expectations.
- Check which certificate covers the public hostname.
- Confirm that the origin accepts the hostname and protocol used by the proxy.
- Review forwarded protocol headers so the application does not mistake HTTPS requests for HTTP.
- Test redirects carefully to avoid an edge-to-origin redirect loop.
What to double-check
Use this verification pass after installation and after every renewal or hosting change.
- Hostname coverage: Confirm the certificate includes the exact domain, www hostname, and subdomains that visitors use. A certificate for the root domain does not automatically cover every subdomain.
- Expiration: Check the certificate’s validity period and confirm who or what is responsible for renewal.
- Chain delivery: An incomplete intermediate chain can cause some browsers, operating systems, or devices to reject the connection even when the certificate appears valid in another browser.
- Private key match: The private key must correspond to the installed certificate. A mismatched key commonly produces a server configuration error.
- Redirect behavior: Test the root domain, www version, common paths, and trailing-slash variations. Each should reach the intended HTTPS URL without repeated redirects.
- Mixed content: Inspect browser developer tools for HTTP images, stylesheets, scripts, fonts, frames, or API requests loaded inside an HTTPS page.
- Canonical and sitemap URLs: Update canonical tags, XML sitemaps, structured data URLs, and internal links where necessary.
- Application functions: Test logins, contact forms, payment flows, webhooks, APIs, password resets, and integrations rather than checking only the homepage.
If the domain was recently connected to a new host, allow for DNS changes to reach different resolvers and test from more than one network. The related domain, DNS, and SSL checklist covers this broader sequence.
Common mistakes
Installing a certificate before DNS points to the right server: Validation may reach an old host or fail altogether. Confirm the active A, AAAA, or relevant alias records first.
Redirecting too early: A redirect can hide the original problem and make troubleshooting harder. Verify that HTTPS works directly before forcing all HTTP requests to it.
Changing only the homepage: Mixed content often remains in templates, uploads, scripts, and third-party embeds. Test representative pages, not just the front page.
Forgetting non-web services: Domain changes can affect email, APIs, staging sites, and verification records. Separate web certificate work from unrelated DNS edits.
Assuming renewal is automatic: A certificate may renew successfully but fail to deploy, or renewal may depend on a validation method that no longer works after a migration. Document the renewal owner, validation path, and post-renewal test.
Using a permanent redirect without a rollback plan: Keep a backup of the previous configuration and know how to disable the redirect if a critical application function fails.
When to revisit
Revisit this SSL certificate setup checklist before a certificate expires, before a seasonal launch, and whenever the hosting, DNS, CDN, or application architecture changes. It is especially useful after moving a website, adding a subdomain, changing the primary domain, enabling a proxy, rebuilding a VPS, or replacing a WordPress theme or major plugin.
For a practical final pass, create a recurring maintenance task with these actions:
- Record certificate expiration dates and renewal responsibility.
- Confirm automatic renewal or schedule a manual renewal reminder.
- Test the root domain, www hostname, key subdomains, and several important URLs over HTTPS.
- Review browser console messages for mixed content and application errors.
- Check redirects, canonical URLs, sitemap references, forms, logins, and integrations.
- Keep the current server, DNS, and application configuration documented.
- Update this checklist when your hosting panel, certificate workflow, proxy, or deployment process changes.
Completing these checks turns HTTPS from a one-time installation task into a repeatable part of website operations. When planning a wider move, combine them with the website migration checklist to reduce the risk of certificate, DNS, or redirect problems during the transition.