Failures and antipatterns · Intermediate

Expired TLS certificates

Check validity periods, verifier time and certificate paths, distinguishing successful issuance from the certificate actually served.

Ask Logeia about this articleTry the three questionsReview your answers

Updated

On this page
  1. Encryption does not establish certificate validity
  2. Check leaf and intermediate validity periods
  3. Inspect the endpoint clients actually reach
  4. Repair renewal without disabling verification
  5. Ask Logeia about this articleCheck your understanding

Encryption does not establish certificate validity

An expired TLS certificate is one possible reason for certificate validation to reject a connection. Being able to exchange encrypted traffic with a key is not the same as establishing a trusted peer identity. Relate the certificate’s notBefore and notAfter values to the verifier’s current time. An apparent expiry problem can also involve an incorrect client clock or another certificate in the validation path. The investigation should identify the failed validity condition rather than treating any TLS error as a generic networking outage or assuming that encryption alone makes the connection trustworthy.

Check leaf and intermediate validity periods

For example, a leaf certificate may remain valid until next month while an intermediate certificate or selected validation path has a validity problem. Conversely, placing a renewed certificate on one server does not help clients if a load balancer still serves the old certificate. Examine each relevant certificate and record hostname, port, time and endpoint. A control panel reporting successful renewal is evidence about an issuance workflow, not conclusive evidence about every TLS terminator that users can actually reach through DNS and traffic routing.

Inspect the endpoint clients actually reach

Inspect the connection with the intended hostname and SNI, then examine subject alternative names, issuer, validity interval and the supplied chain. OpenSSL s_client and x509 can expose useful material, but merely printing a certificate is not proof that normal peer verification succeeded. A corporate proxy or CDN may terminate TLS with a certificate different from the origin’s certificate. Compare the path seen by the affected client, its clock and trust store with a known working path. Preserve these distinctions when multiple clients report apparently inconsistent outcomes.

Repair renewal without disabling verification

Repair the served leaf certificate and required chain at the actual terminator, including any necessary deployment or reload step. Renewal monitoring should verify both issuance and what the public endpoint serves. Disabling validation or deliberately rolling a clock backward discards an identity-checking property instead of fixing the operational cause. Hostname mismatch, revocation and an untrusted issuer are distinct validation failures that may survive a certificate renewal. Confirm a normal verified connection after the repair and test the renewal delivery path before the next expiry rather than waiting for another incident.

Reading and practice are recorded separately in this browser, for each language.

Learn this in order

Understand the systems behind the web · STEP 10

Choose a learning path