Use this reusable checklist to install HTTPS on cloud hosting, renew certificates before they expire, verify coverage for every hostname, and troubleshoot the warnings that can interrupt a website launch or deployment.
Overview
An SSL certificate enables a secure TLS connection between a visitor’s browser and your website. Although people commonly say “SSL,” modern sites use TLS; the practical result is the same: visitors connect over https://, browsers can verify the site’s identity, and data is encrypted in transit.
On cloud web hosting, certificate management may be handled by a hosting control panel, a reverse proxy, a load balancer, a container platform, or the web server itself. Before you install anything, identify which component terminates HTTPS. Installing a certificate on the wrong layer is a common reason for seeing an old certificate, an incomplete certificate chain, or a certificate that does not renew automatically.
Also list every hostname that should work. A certificate for example.com does not automatically cover www.example.com or app.example.com. Decide whether you need the root domain, the www hostname, individual subdomains, or a wildcard such as *.example.com.
Certificate types at a glance
| Certificate type | Useful when | Check before choosing |
|---|---|---|
| Single-domain | One specific hostname needs HTTPS. | Confirm whether the root and www names are both included. |
| Multi-domain | Several named domains or subdomains need coverage. | Track every included hostname and update the certificate when your inventory changes. |
| Wildcard | Many first-level subdomains share a domain. | It normally covers subdomains at one level, not the root domain or deeper nested names unless separately included. |
| Platform-managed | Your cloud host, CDN, proxy, or hosting panel provisions and renews the certificate. | Verify DNS, validation permissions, renewal notifications, and the actual termination point. |
For most websites, an automated certificate managed by the hosting platform is simpler than manual certificate files. Manual installation may still be appropriate for a self-managed VPS, a private service, a special certificate requirement, or an environment where the platform cannot complete validation.
Checklist by scenario
Scenario 1: Enabling HTTPS on a new cloud-hosted website
- Confirm DNS routing. Check that the required A, AAAA, or CNAME records point to the hosting or proxy service that will serve the site. Use a DNS management guide or a DNS propagation checker if records were recently changed.
- Add all hostnames. Enter the root domain,
www, and required subdomains in the hosting panel or certificate configuration. Do not assume a subdomain is covered because the main site is secure. - Complete domain validation. Depending on the platform, validation may use a DNS record, an HTTP file, or an email address. Add only the record or file requested by the platform, and remove temporary validation data when the provider instructs you to do so.
- Install or attach the certificate. Select the certificate for the correct site, load balancer, listener, virtual host, or application route. If installing manually, provide the private key, certificate, and intermediate chain through the platform’s documented fields.
- Redirect HTTP to HTTPS. Test the secure URL first, then configure a permanent redirect from HTTP. Keep exceptions for health checks or internal endpoints only when your architecture requires them.
- Test the complete site. Open the root domain,
www, each important subdomain, common page types, forms, assets, and API endpoints. Confirm that redirects do not create a loop.
Scenario 2: Renewing an existing certificate
- Find the certificate’s expiration date, covered names, issuing system, and renewal owner.
- Check whether renewal is automatic and whether the platform can still complete validation. DNS records, firewall rules, changed load balancers, and removed validation permissions can all interrupt automation.
- Confirm that the account, API token, DNS integration, or deployment permissions used for renewal are still valid.
- Renew or replace the certificate according to the platform workflow. Avoid deleting the active certificate until the replacement is installed and tested.
- Verify the served certificate from outside the hosting console. A successful renewal in one environment does not prove that production is serving the new certificate.
- Record the next expiration date and test alert delivery. Notifications should reach more than one responsible person where practical.
Scenario 3: Installing a certificate on a self-managed VPS
First identify the web server or proxy that handles port 443, such as Nginx, Apache, or another application gateway. Create a secure backup of the current configuration, install the certificate and private key using restricted file permissions, and configure the complete certificate chain. Then validate the configuration before reloading the service.
Typical validation commands include:
openssl s_client -connect example.com:443 -servername example.com -showcerts
curl -I https://example.com
curl -sS -o /dev/null -w "%{http_code} %{url_effective}\n" https://example.com
The first command helps inspect the certificate presented for a specific hostname. The -servername option matters when several sites share one IP address. The curl commands help check the HTTP response and redirect behavior. Interpret results alongside your server logs and hosting dashboard; command output alone may not reveal every application-level issue.
Scenario 4: Adding a new subdomain
Add the DNS record, configure the subdomain in the hosting platform, and include it in the certificate before sending traffic to it. If the certificate is wildcard-based, confirm that the new name matches the wildcard’s coverage. Test the subdomain directly and check that the application generates secure links, callback URLs, cookies, and redirects for the new hostname.
What to double-check
- Hostname coverage: Verify the exact name in the browser certificate viewer. Check both the root domain and
wwwif both are published. - Certificate chain: A server certificate without the required intermediate certificates can work in one client and fail in another. Use the chain format required by your hosting platform.
- Private key matching: The private key must correspond to the certificate. If you generated a new certificate request, keep its matching key with the deployment record.
- DNS and validation: A stale CNAME, conflicting record, DNS proxy, or blocked HTTP validation path can prevent issuance or renewal.
- Clock and environment: Incorrect system time can make a valid certificate appear not yet valid or expired. Check production separately from staging.
- TLS configuration: Prefer the secure protocol and cipher defaults supplied by a maintained hosting platform or current web-server documentation. Remove obsolete protocols only after checking the compatibility needs of your users and integrations.
- Mixed content: A page can have a valid certificate and still load images, scripts, fonts, or API calls over HTTP. Update application URLs and inspect browser developer tools.
- Email and DNS separation: Changing web records should not unintentionally remove MX, SPF, DKIM, or DMARC records. Review the custom-domain email authentication guide before editing DNS.
Common mistakes
Installing the certificate only on staging. Staging may use a different load balancer, container, or DNS name. Validate the production endpoint independently.
Redirecting too early. Configure the HTTPS service and test it before forcing all HTTP traffic to HTTPS. Otherwise, a bad listener or redirect rule can make the site unavailable.
Forgetting alternate hostnames. Visitors may still use www, an old subdomain, or a campaign hostname. Either cover those names or redirect them deliberately to a covered hostname.
Relying on a calendar reminder alone. Manual reminders do not renew certificates. Confirm that the platform’s automation works and that its validation records and credentials remain usable.
Copying a private key into tickets or chat. Treat private keys as secrets. Store them in the hosting platform’s protected secret mechanism or an appropriate secrets manager, and replace a key if exposure is suspected.
Assuming a browser warning always means expiration. The cause may be a hostname mismatch, an incomplete chain, a revoked certificate, a local clock problem, or mixed content. For a broader diagnostic flow, see SSL certificate errors explained.
When to revisit
Review this checklist before every new website or subdomain launch, before changing cloud providers, and before moving a site behind a CDN, proxy, load balancer, or new deployment platform. Revisit it during certificate-renewal reviews, DNS migrations, domain transfers, and major infrastructure changes.
Also update your procedure when your hosting provider changes its certificate panel, validation method, API permissions, or renewal notifications. Certificate authorities, browsers, and platform defaults can change, so avoid hard-coding assumptions about certificate lifetime or renewal timing into an operational runbook. Record the current owner, covered hostnames, termination point, validation method, alert path, and last successful renewal test.
Final action checklist: inventory hostnames; confirm DNS; identify the HTTPS termination point; install or renew the certificate; verify the chain and hostname coverage; test production with a browser, openssl, and curl; check for mixed content; confirm HTTP-to-HTTPS redirects; and document the next review date. Pair this work with your website launch infrastructure checklist and your hosting backup plan so certificate management remains part of the wider cloud operations process.