SSL and HTTPS errors can come from an expired certificate, a domain mismatch, incorrect redirects, incomplete certificate files, or content that still loads over HTTP. This guide provides a practical way to identify the symptom, check the likely cause, renew or replace a certificate safely, and monitor HTTPS after changes to hosting, DNS, WordPress, or a CDN.
Overview
HTTPS protects the connection between a visitor’s browser and your website. An SSL certificate, more accurately part of a TLS setup, helps the browser verify that it is connecting to the intended domain and allows the connection to be encrypted. When that verification fails, the browser or monitoring service may show a security warning instead of loading the page normally.
The wording varies by browser and operating system, but the underlying causes are usually consistent. Before changing settings, record the exact error, the affected URL, when the problem began, and whether it affects every visitor or only a particular device or network. This prevents a local cache or DNS issue from being mistaken for a server configuration problem.
For small business websites, HTTPS should be treated as an ongoing operational check rather than a one-time installation. Certificate expiration dates, DNS records, redirect behavior, CDN settings, and application-generated URLs can all change independently. A simple recurring review reduces the chance that a certificate problem will interrupt customer visits, forms, logins, or checkout.
What to track
Certificate status and coverage
Check the certificate’s expiration date and confirm that it covers every hostname visitors are expected to use. This may include the main domain, a www variant, a staging hostname, or a subdomain used for an application. A certificate for example.com does not automatically cover every possible subdomain. Coverage depends on the certificate’s listed names and any applicable wildcard configuration.
Also verify that the certificate is issued for the domain currently displayed in the address bar. A warning such as “certificate name mismatch” commonly appears when the server returns a certificate for a different hostname, when DNS points to the wrong server, or when a site was moved without updating the certificate configuration.
Certificate chain and server delivery
A server may have the correct certificate but still fail to provide the intermediate certificates needed for browsers to build a trusted chain. If some browsers, devices, or monitoring tools fail while others work, an incomplete chain is one possible explanation. Review the certificate bundle provided by your certificate authority and confirm that the hosting control panel or web server is configured to deliver the required chain.
Do not assume that uploading a new certificate is enough. Record where the private key, certificate, and chain are installed, who has access to them, and whether a load balancer, reverse proxy, or CDN also needs an update. Never publish or share a private key.
Redirects and canonical HTTPS behavior
A healthy site normally has one deliberate preferred URL, such as https://www.example.com or https://example.com. Test these variations:
http://example.comhttp://www.example.comhttps://example.comhttps://www.example.com
Check whether each non-preferred version reaches the preferred version without repeated hops. A redirect loop can occur when the CDN terminates HTTPS but the origin server believes the request is HTTP, or when separate redirect rules conflict. Review proxy settings, forwarded-protocol headers, application URL settings, and web-server rules together rather than changing them one at a time without a test.
Mixed content
Mixed content occurs when an HTTPS page requests a resource over HTTP. Images, stylesheets, scripts, fonts, video files, embedded content, and third-party integrations can all cause it. Browsers may block active content such as scripts or forms, while less sensitive resources may produce a warning or be upgraded automatically.
Use the browser’s developer tools to identify the exact HTTP resource. Replace hard-coded http:// URLs with HTTPS where the resource supports it, update content-management-system settings, and check theme or plugin configuration. For WordPress websites, review the site URL, home URL, media references, database content, and any integration that generates absolute URLs. Test changes on staging when possible; the WordPress staging and safe update workflow can help reduce risk.
CDN and origin certificates
When a CDN or reverse proxy sits between visitors and the hosting server, there may be two TLS connections: browser to CDN and CDN to origin. Both need an appropriate configuration. A browser-facing certificate can be valid while the origin certificate is expired, missing, or issued for the wrong hostname. Conversely, an origin may be configured correctly while the CDN continues serving an old certificate.
Document which service terminates HTTPS, which hostname it uses to contact the origin, and whether the origin requires certificate validation. After changes, purge relevant caches only if necessary and verify the public endpoint from outside the hosting environment.
Symptom-to-cause checklist
| Symptom | Likely areas to inspect | First practical check |
|---|---|---|
| Certificate expired | Renewal process, scheduled automation, hosting configuration | Confirm the served certificate’s expiration date, then renew and install the replacement. |
| Certificate name mismatch | DNS, hostname coverage, virtual-host configuration | Compare the address-bar hostname with the names listed on the served certificate. |
| Some devices report an untrusted certificate | Incomplete chain, outdated trust store, proxy inspection | Check whether the server delivers the required intermediate certificates. |
| HTTPS redirects repeatedly | CDN mode, origin protocol, application and server rules | Trace each redirect and identify where the protocol changes back to HTTP. |
| Page loads but shows a security warning | Mixed content, embedded resources, forms | Use browser developer tools to locate HTTP requests on the HTTPS page. |
| Visitors fail after a CDN change | Edge certificate, origin certificate, DNS, cache | Test the public hostname and origin path separately, if your setup permits it. |
Cadence and checkpoints
Use a monthly or quarterly HTTPS review, with a shorter interval when the site changes frequently. At each review, record the certificate expiration date, covered hostnames, redirect destination, HTTP response behavior, and the status of important forms or login pages. Keep the results in the same maintenance log used for backups and uptime checks.
Set a reminder well before expiration rather than relying on the day-of renewal. The exact lead time depends on the certificate authority, hosting platform, and whether renewal is automated. Confirm that automation has both permission to renew and a way to install the renewed certificate. A successful renewal at the certificate authority does not necessarily mean the new certificate is being served publicly.
After a domain move, DNS change, hosting migration, CDN change, WordPress URL update, or server rebuild, run an additional HTTPS check. Test from an external network and use more than one browser or monitoring location when possible. Pair this review with your website uptime monitoring and incident response process, since certificate failures can appear as downtime to visitors.
How to interpret changes
Compare the current result with the previous known-good result. If only one hostname fails, investigate its DNS record, virtual host, and certificate coverage. If all hostnames fail immediately after a hosting change, inspect the server or CDN TLS configuration before editing page content. If the error appears only on one device, test its clock, network, cached HSTS policy, security software, and trust-store state.
Separate connection-level problems from page-level problems. An expired certificate, name mismatch, or broken chain usually prevents a secure connection from being established. Mixed content usually occurs after the connection succeeds and is visible in page resources. Redirect loops sit between these layers: the TLS connection may work, but the server and application disagree about the desired protocol or hostname.
Be cautious with temporary workarounds. Disabling certificate verification, accepting a browser warning, or switching a CDN to a less strict origin mode may help isolate a cause, but these settings should not be treated as a permanent fix. Restore the intended verification and document any temporary change. When troubleshooting WordPress, take a backup and test configuration changes in a controlled environment; the website hosting backup strategy guide covers the broader backup considerations.
When to revisit
Revisit this checklist monthly or quarterly, depending on how often the website and hosting stack change. Review it immediately when a browser displays a security warning, a monitor reports TLS failure, a certificate authority sends a renewal notice, or a customer cannot reach a form or checkout page.
Add an extra checkpoint after changing the domain, DNS provider, hosting plan, web server, CDN, WordPress URL, plugins that generate links, or third-party embeds. These changes can affect HTTPS even when the site’s visible design remains the same. If your site is growing or experiencing more traffic, review HTTPS alongside capacity and performance planning rather than treating security and hosting as separate tasks. The shared hosting upgrade checklist and VPS sizing guide provide useful context for that review.
For each checkpoint, complete this short action list:
- Open the preferred HTTPS URL and record the result.
- Inspect the certificate expiration date and hostname coverage.
- Test HTTP and alternate-hostname redirects for loops or unexpected destinations.
- Check browser developer tools for mixed-content requests.
- Verify CDN and origin TLS settings after infrastructure changes.
- Record the date, findings, owner, and next renewal or review date.
A repeatable log turns SSL certificate troubleshooting from an emergency reaction into routine website maintenance. When a problem does occur, the recorded baseline makes it easier to identify what changed and restore a reliable HTTPS configuration without guessing.