7 Common Pitfalls with SSL Certificates and HTTPS

HTTPS issues rarely come from buying the wrong certificate — they usually happen after installation. An incomplete certificate chain, mixed content, incorrect r…

Insights:7 Common Pitfalls with SSL Certificates and HTTPS

Pitfall 1: Installed only the certificate, not the intermediate certificate

The server returns only the site certificate and not the intermediate certificate, causing some browsers and mobile devices to report "incomplete certificate chain".

Check: Use an online chain checker tool or command line to inspect the returned certificate chain and confirm it includes the intermediate certificate.

Pitfall 2: Mixed HTTP resources in the page

Images, scripts, stylesheets, and fonts still load over HTTP, causing the lock icon to disappear; some browsers block them outright.

Check: Open Developer Tools, filter for mixed content, and change internal resource URLs to relative protocol or HTTPS absolute addresses.

Pitfall 3: Only the homepage is on HTTPS

The homepage redirects to HTTPS, but inner pages remain HTTP, leaving users unprotected when they arrive at inner pages from search results.

Check: Crawl the entire site and confirm all entry points 301-redirect to HTTPS, with only a single redirect.

Pitfall 4: Redirect written as a loop

HTTP redirects to HTTPS, then HTTPS loops back to HTTP; or www and non-www redirect to each other, resulting in ERR_TOO_MANY_REDIRECTS.

Check: Use curl -I to inspect status codes and Location headers hop by hop, ensuring the chain is unidirectional.

Pitfall 5: Renewal Relies on Manual Reminders

No expiry alerts mean holidays go unattended and the site goes down entirely.

Check: Set up alerts at 30/14/7 days before expiry, auto-reload after renewal, and assign clear ownership.

Pitfall 6: Wrong Wildcard Certificate Scope

A wildcard only covers one subdomain level; *.example.com does not cover a.b.example.com.

Check: List all live domains and verify each against the certificate SAN list.

Pitfall 7: Premature HSTS Preload Enablement

If the site still has an HTTP entry or subdomain that hasn’t been migrated, submitting HSTS preload is very difficult to roll back.

Check: Start with a short max-age canary release, confirm all subdomains are stable over HTTPS, then consider extending the age and enabling preload.

Troubleshooting Order

  1. Check the browser error type.
  2. Verify certificate validity period and domain match.
  3. Check whether the certificate chain is complete.
  4. Check for mixed content on the page.
  5. Inspect redirect chains.
  6. Check HSTS and CDN configurations.

Boundaries

Different clients, CDNs, and load balancers handle certificates differently. The above is a general troubleshooting order; specific fixes should be based on your actual chain and devices.

Related reading: