This HTTPS and SSL certificate manual provides a reusable checklist for installing a certificate, enabling HTTPS, renewing it, fixing browser warnings, and redirecting HTTP traffic safely. Use the workflow that matches your hosting setup, and keep a rollback path before changing production configuration.
Overview
HTTPS protects the connection between a visitor’s browser and your website. It depends on a TLS certificate, although people still commonly call it an SSL certificate. The certificate must cover the hostname being visited, remain within its validity period, and be presented with a trusted certificate chain. Your web server or reverse proxy must also be configured to use the certificate’s private key and to serve HTTPS on the expected port.
Before starting, record the domains and subdomains that need HTTPS, such as example.com, www.example.com, app.example.com, and an administrative hostname. Confirm where DNS is managed, where TLS terminates, and whether a content delivery network, load balancer, or reverse proxy sits in front of the application. These details determine where the certificate must be installed.
Certificate types at a glance
| Certificate type | Typical use | Important consideration |
|---|---|---|
| Single-domain | One hostname, such as www.example.com | Other hostnames require separate coverage. |
| Wildcard | Multiple subdomains under one domain, such as *.example.com | It normally covers one subdomain level, not the bare domain automatically. |
| Multi-domain or SAN | Several explicitly listed hostnames | Every required hostname must be included in the certificate. |
| ACME-managed certificate | Automated issuance and renewal through an ACME client | DNS or HTTP validation and renewal permissions must continue working. |
The right choice depends on your hostname list and operational needs, not on the label alone. For many sites, automated certificate management is easier to maintain than manually uploading replacement files, provided renewal monitoring is in place.
Checklist by scenario
Shared hosting or a hosting control panel
- Back up the current site configuration and note the existing certificate status.
- Verify that DNS for each hostname points to the intended hosting account. A certificate cannot be used successfully if the hostname resolves to another server or proxy.
- Open the hosting panel’s SSL, TLS, Security, or Certificates area. Menu names vary by provider.
- Choose the provider’s managed certificate option when available, or select the manual installation option if you already have a certificate, private key, and certificate-chain file.
- Enter the files in the correct fields. Do not paste a private key into a certificate or chain field, and do not share the private key through an unsecured channel.
- Apply the certificate to every required hostname, including both the bare domain and the
wwwhostname when both are used. - Open each HTTPS hostname in a private browser window. Confirm that the expected page loads and that the browser reports a valid connection.
- Only after HTTPS works, configure the HTTP-to-HTTPS redirect in the panel or application settings.
Reverse proxy, load balancer, or CDN
- Identify the TLS termination point. If the proxy handles HTTPS, the public certificate belongs there, even if the origin server also uses HTTPS.
- Install or attach the certificate at the proxy and confirm that its hostname list matches the public hostnames.
- Decide whether the proxy-to-origin connection is HTTP or HTTPS. HTTPS to the origin provides an additional encrypted connection, but the origin must have a suitable certificate and trust configuration.
- Preserve the original host and protocol headers as required by the application. Frameworks often need a trusted proxy setting to generate HTTPS links correctly.
- Test the public endpoint, the origin endpoint where appropriate, redirects, login flows, webhooks, and static assets.
- Do not enable a strict transport policy or equivalent browser-enforcement setting until all required subdomains and redirect paths have been tested.
Apache
Enable the SSL module and the HTTPS virtual host using the method provided by your operating system. In the HTTPS virtual host, specify the certificate, private key, and any required intermediate chain. A simplified configuration pattern looks like this:
<VirtualHost *:443>
ServerName example.com
ServerAlias www.example.com
SSLEngine on
SSLCertificateFile /path/to/certificate-chain.pem
SSLCertificateKeyFile /path/to/private-key.pem
DocumentRoot /var/www/example
</VirtualHost>File directives and module names can differ by distribution. Validate the configuration before reloading the service, then test both hostnames. Keep the HTTP virtual host available long enough to issue a controlled redirect and to handle any required validation path.
Nginx
In the HTTPS server block, define the certificate and key, then reload only after testing the configuration:
server {
listen 443 ssl;
server_name example.com www.example.com;
ssl_certificate /path/to/certificate-chain.pem;
ssl_certificate_key /path/to/private-key.pem;
root /var/www/example;
}Use your platform’s configuration-test command before reloading Nginx. A syntax error can prevent the service from reloading, while an incorrect certificate path can cause startup or reload failure.
ACME or Let’s Encrypt-style automation
- Choose an ACME client supported by your server or hosting platform.
- Use HTTP validation only when the required hostname reliably reaches the validation directory. Use DNS validation when the web server is unavailable, traffic is proxied in a way that blocks validation, or wildcard coverage is required.
- Grant the client only the DNS or server permissions it needs.
- Run a renewal simulation or staging test when the client supports one.
- Confirm that renewal is scheduled and that a successful renewal reloads the proxy or web server.
- Set an alert based on certificate expiry or failed renewal rather than assuming automation will remain healthy.
What to double-check
Certificate coverage and chain
Check the certificate’s subject alternative names, not just its displayed common name. A certificate for www.example.com may not cover example.com or api.example.com. Also verify that the server sends the intermediate certificates required by clients. A certificate can appear valid in one browser or operating system while presenting chain problems elsewhere.
From a system with OpenSSL available, an inspection command can help reveal the presented certificate and chain:
openssl s_client -connect example.com:443 -servername example.com -showcertsReview the certificate names, dates, issuer information, and verification output. Use an external TLS checker or browser developer tools as a second view, especially when a proxy or CDN is involved.
Renewal readiness
- Confirm the renewal account, API credentials, and contact or alert destination.
- Check that DNS records have not moved since the last successful issuance.
- Verify that port 80 or the DNS API remains available for the selected validation method.
- Confirm the renewed certificate is actually installed after issuance.
- Reload the service gracefully and test the public endpoint.
- Document who receives failure alerts and how to perform a manual replacement.
Mixed content diagnosis
Mixed content occurs when an HTTPS page requests an HTTP image, stylesheet, script, font, iframe, API endpoint, or other resource. Open browser developer tools and inspect the Console and Network panels. Search the page source, templates, CSS, JavaScript, database content, and environment variables for absolute http:// URLs. Replace them with HTTPS or protocol-relative application logic where appropriate, update canonical and asset URLs, and clear caches.
Do not blindly upgrade every resource. A third-party endpoint may not support HTTPS, and changing it can break the page. Replace, remove, or proxy an insecure dependency only after confirming its purpose and compatibility.
Redirect behavior
Test these combinations separately: HTTP bare domain, HTTP www, HTTPS bare domain, and HTTPS www. Decide which hostname is canonical, then redirect all other variants to it in one step where possible. Avoid redirect loops caused by a proxy reporting the wrong original protocol to the application.
A generic Nginx redirect pattern is:
server {
listen 80;
server_name example.com www.example.com;
return 301 https://example.com$request_uri;
}Adapt the target hostname and syntax to your server. Test query strings, deep links, trailing slashes, login pages, API routes, and file downloads. Use a temporary redirect while testing if you need an easy rollback; use a permanent redirect only after the destination is confirmed.
Common mistakes
- Installing the certificate on the wrong layer: The certificate is placed on the origin while a CDN or load balancer continues serving an expired certificate publicly.
- Forgetting a hostname: The main domain works, but
www, an API subdomain, or a mail-related web interface still shows a warning. - Uploading the wrong chain: The server sends only the leaf certificate and omits intermediate certificates.
- Replacing files without reloading: The new certificate exists on disk, but the running service still presents the old one.
- Redirecting too early: HTTP validation, health checks, staging paths, or application callbacks fail after a blanket redirect.
- Ignoring the private key: Permissions are too broad, the key does not match the certificate, or it is lost before renewal.
- Trusting one successful browser test: A cached certificate, different hostname, or different network path hides a problem.
- Enabling strict browser policies prematurely: A forgotten subdomain can become difficult to access after enforcement is enabled.
Before changing production settings, export the current configuration, record the active certificate fingerprint or expiry date, and confirm that you have console or hosting-panel access if the web server fails to reload.
When to revisit
Use this checklist before every planned certificate renewal, DNS change, hosting migration, proxy change, or subdomain launch. Revisit it after a browser reports a certificate warning, after changing application URL settings, and during recurring HTTPS security audits. Also review it whenever your ACME client, hosting panel, CDN, web server, or DNS provider changes its workflow.
For a practical maintenance routine, keep a hostname inventory and certificate-expiry dashboard, test renewal in a non-production environment when possible, and schedule a reminder well before expiry. On each review, run this sequence:
- List every public hostname and identify its TLS termination point.
- Inspect the currently served certificate and chain.
- Run or simulate renewal.
- Test HTTP and HTTPS redirects for canonical and alternate hostnames.
- Scan representative pages for mixed content.
- Check application callbacks, APIs, webhooks, and monitoring probes.
- Record the result, any changed configuration, and the rollback procedure.
Keeping these notes with your deployment documentation turns SSL certificate renewal from an emergency task into a repeatable setup and troubleshooting process.