Common TLS/SSL Certificate Problems and How to Fix Them

Almost every TLS certificate failure — SSL, as the industry still calls it — falls into one of six buckets: hostname mismatch, incomplete chain, key mismatch, expiry, untrusted source, or mixed content. Each has a precise fix, and all of them can be diagnosed in minutes with free tools: the SSL Checker, Certificate Decoder and Certificate & Key Matcher. Here is how to identify and solve each one.
Problem 1: Hostname Mismatch
ERR_CERT_COMMON_NAME_INVALID means the name you visited is not in the certificate's Subject Alternative Names. Modern browsers match hostnames against SANs only (RFC 9525 replaced the old CN rules in 2017–2018). Fix: regenerate the CSR with every served hostname listed as a SAN — the CSR Generator takes them as plain form fields. Note that a wildcard *.example.com covers one level only, not a.b.example.com.
Full fix: Hostname Mismatch: SSL Common Name and SAN Errors
Problem 2: Incomplete Certificate Chain
Your server sends the leaf certificate but not the intermediates, so desktop browsers may still trust it (they cache intermediates) while mobile browsers and API clients fail with ERR_CERT_AUTHORITY_INVALID. Fix: install the full fullchain bundle your CA provides, then re-run the SSL Checker, which reports exactly what the server is missing.
Full fix: Incomplete Certificate Chain: Fix the Missing Intermediate
Problem 3: Private Key Mismatch
nginx: [emerg] key values mismatch or an Apache SSL library error means the installed certificate does not pair with the private key — usually a leftover from a previous issuance. Fix: verify the pair with the Certificate & Key Matcher; if the original key is gone, generate a new CSR with the CSR Generator and reissue.
Full fix: How to Check a Certificate Matches Its Private Key
Problem 4: Expired Certificate
ERR_CERT_DATE_INVALID means the validity window has passed. Lifetimes are shrinking — 200 days maximum since 2026-03-15, 100 days from 2027-03-15 and 47 days from 2029-03-15 (CA/Browser Forum SC-081v3) — so manual renewals fail more often. Fix: renew now, automate with ACME, and add the Expiry Monitor so you are never surprised again.
Full fix: Certificate Expired: How to Renew and Redeploy Fast
Problem 5: Self-Signed or Untrusted Root
ERR_CERT_AUTHORITY_INVALID on a brand-new certificate often means a self-signed certificate is being served in production, or an internal root CA that visitors do not trust. Self-signed is fine for local development; production needs a publicly trusted CA. Fix: issue a proper certificate via the CSR Generator and install it together with its chain.
Full fix: Self-Signed Certificates: Trust Errors in Browsers and Apps
Problem 6: Mixed Content
The padlock turns into "Not secure" because the HTTPS page loads images, scripts or iframes over HTTP, and browsers block active mixed content outright. Fix: rewrite asset URLs to HTTPS, clean hardcoded http:// references in the CMS, and add a Content-Security-Policy: upgrade-insecure-requests header as a safety net.
Full fix: Mixed Content Errors: Why They Happen and How to Fix Them
Five Steps to Diagnose Any Certificate Problem
Step 1: Get the Full Picture with the SSL Checker
Enter the hostname in the SSL Checker. It shows the served chain, expiry, SANs, protocol versions and cipher suites — enough to classify the problem immediately.
Step 2: Inspect the Certificate Details
Paste the PEM into the Certificate Decoder to read exact subjects, SANs and validity dates without leaving your browser.
Step 3: Verify the Key–Certificate Pair
Run the Certificate & Key Matcher to confirm the private key matches the certificate before blaming the server.
Step 4: Fix the Root Cause
Regenerate the CSR with correct SANs, install the full chain, replace the mismatched key, or renew — depending on what steps 1–3 revealed.
Step 5: Prevent Recurrence
Set up expiry monitoring, adopt ACME auto-renewal, and re-run the SSL Checker after every deployment so regressions surface immediately.
Troubleshooting Checklist
| Symptom | Likely cause | How to fix |
|---|---|---|
ERR_CERT_COMMON_NAME_INVALID | Visited hostname missing from SAN | Regenerate the CSR listing all hostnames; reissue and reinstall |
ERR_CERT_AUTHORITY_INVALID | Incomplete chain or self-signed certificate | Install the intermediate bundle; use a publicly trusted CA |
ERR_CERT_DATE_INVALID | Certificate expired | Renew, automate with ACME, add expiry monitoring |
key values mismatch at server start | Certificate and private key don't pair | Match the files with the Certificate & Key Matcher; reissue if the key was lost |
| Padlock shows "Not secure" on parts of the page | Mixed HTTP content | Convert asset URLs to HTTPS; add upgrade-insecure-requests |
| Works in desktop Chrome, fails on mobile | Desktop cached the intermediate, mobile did not | Fix the chain on the server; confirm with the SSL Checker |
| CA rejects the CSR at order time | Malformed subject or missing SANs | Decode and verify the CSR first with the Certificate Decoder |
FAQ
Why is my certificate still "not secure" after installing it?
Usually the page mixes HTTP assets (mixed content) or the chain is incomplete. Run the SSL Checker to inspect the chain, and audit the page's network requests for `http://` URLs.
Can an expired certificate be repaired?
No — expiry cannot be undone. Renew or reissue the certificate and install the new one. With validity periods heading to 47 days, automation is the only sustainable approach.
Do I need a new CSR for every renewal?
A fresh CSR is best practice: it takes seconds and keeps the key pair current. Reusing an old CSR only works if nothing changed and you still hold its private key.
Hasn't revocation checking changed recently?
Yes.Chrome 148 (2026-05-05) stopped counting SCTs delivered inside a stapled OCSP response; Chrome's revocation checks have always relied on CRLSets rather than live OCSP queries. Check CRL-based status with the [Revocation Checker](/tools/revocation) — and treat revocation as a fallback, with expiry monitoring as your primary defense.
Free SSL/TLS tools
Verify and inspect your certificates in seconds.
Related Certificate Info
Learn more about choosing and buying certificates.