Back to Articles
Troubleshooting2026-08-12•3 min read•CSR.plus Team

Common SSL Errors & Fixes: Expiry, Mismatch, Chain, Mixed Content

Common SSL Errors & Fixes: Expiry, Mismatch, Chain, Mixed Content

Common SSL Errors

The most common browser SSL/TLS (still commonly called SSL) warnings come from expired certificates, hostname mismatches, and incomplete certificate chains; mixed content is a page-level problem of HTTP resources loaded inside an HTTPS page. Before changing anything, use the SSL Checker to see exactly which error your certificate triggers.

Expired certificate

Once a certificate passes its validity, browsers refuse the connection and show a security warning. With validity shrinking from 200 to 100 to 47 days (CA/B Forum SC-081v3, 2025), manual renewal is easy to forget — automation is the key defense.

Hostname mismatch

"Certificate name does not match" appears when the certificate covers a different domain than the one requested. Fix it by issuing for the exact hostname or adding the name as a SAN; a wildcard covers many subdomains at once.

Incomplete chain / untrusted issuer

The server sent only the leaf certificate or an intermediate is missing, so clients cannot build a path to a trusted root. Install the full chain — leaf plus intermediates, in the correct order.

Mixed content

An HTTPS page that loads scripts, styles, or images over HTTP triggers the padlock warning, and browsers may block the request entirely. Change http:// references to https:// or protocol-relative URLs.

Handshake and protocol errors

TLS handshake failures usually come from mismatched protocol versions or cipher suites: an old client against a strict modern server, or vice versa. Keep TLS 1.2 and TLS 1.3 enabled with modern ciphers.

Step 1: Pinpoint the exact error

Use the SSL Checker to inspect expiry, chain completeness, hostname coverage and protocol versions, and identify which problem you face.

Step 2: Fix expiry or chain issues

Renew and install a new certificate if expired; if the chain is incomplete, inspect with the Certificate Decoder and add the missing intermediate in the right order.

Step 3: Fix hostname and mixed content

Re-issue for the exact hostname or add a SAN; change http:// resource URLs in the HTML to https://, or use CSP upgrade-insecure-requests to auto-upgrade.

Step 4: Troubleshoot handshake and protocol

Enable TLS 1.2/1.3 with modern ciphers, and use the SSL/TLS Tracer to see the exact negotiation failure and confirm legacy clients can fall back.

Troubleshooting

ProblemLikely causeFix
Certificate expiredForgotten manual renewalRenew and install; automate with an ACME client
Certificate name mismatchDomain not in CN/SANIssue for the exact hostname or add a SAN; use a wildcard for subdomains
Incomplete chainMissing intermediateAdd the intermediate with the Certificate Decoder
Mixed content warningPage loads http:// resourcesSwitch to https:// or protocol-relative URLs; re-test console
Handshake failedProtocol/cipher mismatchEnable TLS 1.2/1.3; troubleshoot with the SSL/TLS Tracer
Issuer not trustedSelf-signed or unknown rootInstall a trusted chain or use a publicly trusted CA

Next steps

FAQ

Why does my site error on some devices but not others?

Different clients support different TLS versions and ciphers. Old devices often fail against modern-only configs — check the handshake with the [SSL/TLS Tracer](/tools/ssl-tracer).

How do I fix mixed content quickly?

Search the HTML for http:// resource URLs and change them to https://. CSP upgrade-insecure-requests can also auto-upgrade them in modern browsers.

Will your SSL Checker detect all these problems?

It checks expiry, chain completeness, hostname coverage, protocol versions and key match — the common causes of warnings — and points you to the exact failure.

Free SSL/TLS tools

Verify and inspect your certificates in seconds.

Related Certificate Info

Learn more about choosing and buying certificates.

Related articles