SSL Certificate Errors Explained: Diagnose Expired, Mismatched, Untrusted, and Incomplete Certificates
SSLTLSHTTPScertificatesweb securityOpenSSL

SSL Certificate Errors Explained: Diagnose Expired, Mismatched, Untrusted, and Incomplete Certificates

TTecksite Editorial Team
2026-11-13
7 min read

Diagnose HTTPS certificate errors with a practical checklist for expiry, mismatches, trust, chains, TLS settings, and CDN termination.

An HTTPS warning usually points to a specific failure: an expired certificate, a hostname mismatch, an incomplete chain, an untrusted issuer, or a problem somewhere between the browser and the origin server. This checklist shows how to identify the failure, inspect the certificate with browser tools and command-line utilities, and fix the correct server, DNS, CDN, or proxy layer without guessing.

Overview

An SSL certificate, more accurately called a TLS certificate, helps a browser verify that it is connecting to the intended hostname and establish an encrypted connection. HTTPS can fail even when a certificate file exists on the server because several inputs must agree:

  • The certificate must be within its validity period.
  • The requested hostname must appear in the certificate's Subject Alternative Name list.
  • The browser must be able to build a trusted chain from the server certificate through any required intermediate certificates to a trusted root.
  • The server must support a compatible TLS version and cipher configuration.
  • The certificate must be installed at the TLS termination point that actually receives the request.
  • The client device must have a reasonably accurate date and time.

The last point is easy to miss in modern deployments. DNS may send a visitor to a CDN, load balancer, reverse proxy, or hosting platform rather than directly to the application server. The certificate to inspect is therefore the one presented by the public endpoint, not necessarily the certificate stored on the origin machine.

Start with the exact browser message, the affected hostname, and whether the problem affects every visitor or only one device. Do not treat a generic “connection is not private” warning as proof that the certificate itself is expired.

Checklist by scenario

1. The certificate is expired or not yet valid

Typical messages include “ERR_CERT_DATE_INVALID” or a warning that the certificate has expired. Open the certificate details in the browser and check the “Not Before” and “Not After” values. Also verify the computer, phone, server, and monitoring system clocks. A device with an incorrect date can reject an otherwise valid certificate.

To fix the problem, renew the certificate through the certificate authority or your hosting, CDN, or platform provider. Then install the renewed certificate and its private key at the active TLS termination point. Confirm that an automated renewal job completed successfully and that the web server was reloaded if the platform requires a reload.

2. The hostname does not match

A hostname mismatch commonly produces “ERR_CERT_COMMON_NAME_INVALID” or a similar message. Check the address in the browser against the certificate's Subject Alternative Name entries. For example, a certificate for www.example.test does not automatically cover example.test, and a certificate for api.example.test does not cover app.example.test.

Check every public hostname separately, including the apex domain, www version, API hostname, staging hostname, and any custom domain. If a redirect happens after the TLS connection, the first hostname still needs a valid certificate. Install a certificate that explicitly covers the requested names, or correct the DNS and routing configuration if the request is reaching the wrong endpoint.

3. The browser does not trust the issuer

Messages such as “ERR_CERT_AUTHORITY_INVALID” can indicate a self-signed certificate, an internal certificate authority, an untrusted issuer, or a missing intermediate certificate. Public production sites generally need a certificate issued by a certificate authority trusted by the intended client devices. Internal applications may intentionally use an internal authority, but its root certificate must be distributed through a controlled device-management process.

For a public site, confirm that the server is not presenting a development or self-signed certificate. For an internal site, confirm that the connecting device has the expected trust store and that the certificate was issued for the exact internal hostname.

4. The certificate chain is incomplete

A certificate chain error occurs when the server sends its leaf certificate but omits an intermediate certificate that the client needs to connect it to a trusted root. Some browsers may appear to work because they have previously cached or retrieved the intermediate; other clients, command-line tools, or monitoring systems may fail.

Install the server certificate together with the required intermediate certificates in the order specified by the certificate authority. Do not normally copy a root certificate into the server's chain file unless the provider's documentation specifically requires it. After deployment, test from a clean client or a separate network so a cached chain does not hide the problem.

5. The wrong layer has the certificate

If a site uses a CDN, reverse proxy, load balancer, or managed hosting service, inspect the layer that terminates TLS. A valid certificate on the origin does not repair an expired certificate at the CDN edge. Conversely, replacing an origin certificate will not help if DNS still points to an old load balancer.

Observed situationFirst layer to inspect
All visitors see the same certificate errorPublic DNS target and TLS termination service
Only one hostname failsVirtual host or hostname-specific certificate binding
Origin works directly but public URL failsCDN, proxy, or load balancer certificate
Only one backend or region failsThat node's certificate and deployment configuration
Only one device failsDevice clock, trust store, proxy, or security inspection software

6. TLS negotiation fails

Errors such as “ERR_SSL_VERSION_OR_CIPHER_MISMATCH” may be caused by incompatible TLS versions, unsupported cipher suites, an incorrectly configured proxy, or a server that is not speaking TLS on the expected port. Check the web server or platform configuration and compare it with the requirements of the clients you need to support. Avoid changing several TLS settings at once; record the original configuration and test one controlled change at a time.

7. HTTPS works, but page resources are blocked

If the page loads securely but scripts, images, stylesheets, or fonts are blocked, inspect the browser console for mixed-content warnings. Update hard-coded http:// resource URLs to HTTPS, use relative or secure URLs where appropriate, and check third-party integrations. This is different from a certificate error: the TLS connection may be valid while individual resources are requested insecurely.

What to double-check

Inspect the public certificate with OpenSSL

From a system with OpenSSL installed, request the certificate presented for a hostname:

openssl s_client -connect example.com:443 -servername example.com -showcerts

The -servername option is important when the server hosts multiple domains. Without Server Name Indication, you may receive a default certificate that belongs to a different hostname. Review the subject, Subject Alternative Name values, validity dates, issuer, and certificates returned after the leaf certificate.

For a compact date and subject check, you can pipe the first certificate to OpenSSL:

openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null | openssl x509 -noout -subject -issuer -dates

Compare curl with the browser

Use curl to test certificate validation from the client environment:

curl -Iv https://example.com/

Look for the negotiated protocol, certificate subject, issuer, and the point at which verification fails. Do not use -k or --insecure as a fix. Those options suppress verification and can conceal the production problem; they are useful only for controlled diagnostic comparisons.

Check DNS and redirects

Resolve the hostname and follow its redirect path. A DNS change may still be propagating, or an old record may direct some clients to a previous server. Check both the apex domain and subdomains, then test the final HTTPS URL as well as the initial URL. For broader deployment guidance, see Tecksite's domain, DNS, hosting, and SSL deployment checklist.

When investigating an API or application request, browser network tools can show the requested hostname, redirect chain, and failed resource. The Chrome DevTools Network tab guide provides a reusable workflow for that inspection.

Common mistakes

  • Renewing the wrong certificate: The certificate may be valid on the origin while the CDN or load balancer still serves an older one.
  • Checking only one hostname: Apex, www, API, staging, and customer-specific domains can have separate bindings.
  • Installing only the leaf certificate: Clients often need the intermediate chain sent by the server.
  • Testing through a cached path: A browser cache, corporate proxy, or CDN edge can show a different result from a clean client.
  • Disabling verification: Ignoring certificate errors makes a test pass without establishing that HTTPS is correctly configured.
  • Changing DNS and TLS simultaneously: Make one change, record the time and target, then verify which endpoint answered.
  • Assuming the error is application-level: TLS negotiation happens before HTTP headers, routes, APIs, or application logs can help.

When to revisit

Use this checklist before planned certificate renewals, domain migrations, hosting changes, CDN configuration changes, and staging-to-production launches. Revisit it after a certificate authority changes its issuance workflow, after a web server or proxy upgrade, or whenever monitoring reports a certificate that differs from the one expected.

Keep a small certificate inventory with each hostname, termination layer, issuing authority, expiration date, renewal owner, and rollback procedure. Add an external HTTPS check that validates the hostname, expiration window, and chain rather than merely confirming that port 443 is open. Test from more than one network when the service is business-critical.

When an incident occurs, save the exact browser message, the output of openssl s_client and curl -Iv, the resolved DNS target, and the deployment change that preceded the failure. That record turns the next SSL certificate error from a vague browser warning into a repeatable TLS debugging task.

Related Topics

#SSL#TLS#HTTPS#certificates#web security#OpenSSL
T

Tecksite Editorial Team

Technical Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.