Insights:SSL Certificate & HTTPS Troubleshooting: 5-Step Method
Step 1: Check the Error Type
Browser errors generally fall into three categories:
- Certificate has expired or is untrusted.
- Domain name mismatch.
- Connection blocked or abnormal redirect.
The error type determines which layer to investigate next—don't reinstall the certificate right away.
Step 2: Check Validity Period and Domain
openssl s_client -connect example.com:443 -servername example.com
Check notBefore, notAfter, and the SAN list. Confirm:
- The current time falls within the validity period.
- SAN covers the accessed domain.
- Wildcard level matches.
Step 3: Check the Certificate Chain
Add the -showcerts flag to the same command to confirm the output includes not just the site certificate but also the intermediate certificate(s).
Typical signs of an incomplete chain: the site opens in a browser, but mobile devices or some clients throw errors; online checker tools report “chain incomplete.”
Step 4: Check for Mixed Content
The page loads but the lock icon is missing, usually because images, scripts, stylesheets, or fonts are still being served over HTTP.
Filter for http:// resources in DevTools and update each to HTTPS or a relative URL. Be aware that images and fonts referenced inside CSS can also slip through.
Step 5: Check for Redirect Loops
curl -IL https://example.com
Confirm:
- HTTP redirects to HTTPS with a single hop.
- Only one canonical domain is used (www or non-www).
- No redirect from HTTPS back to HTTP.
- No circular multi-hop redirects.
Common Issues Reference
| Issue | Possible Cause | Check First |
|---|---|---|
| Entire site unreachable | Certificate expired or wrong port | Validity period, port 443 listening |
| Only mobile shows errors | Incomplete chain | Intermediate certificate |
| Lock icon missing | Mixed content | Page resource protocols |
| Too many redirects | Rule conflicts | curl hop-by-hop |
| Some subdomains fail | Domain not covered | SAN list |
Post-Fix Verification
- Visit once from both desktop and mobile.
- Online chain validation passes.
- Inner pages and login page work correctly.
- Redirects complete in a single hop.
- Monitoring alerts are cleared.
Limitations
Certificate behavior varies across different clients and CDNs. Command output only validates the current connection path and cannot account for all user environments; critical services should be verified across multiple endpoints.
Related Reading: