Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Security

TLS chain troubleshooting: fix incomplete or untrusted certificate paths

Published August 2026 · 2 min read · Updated 2026-09-05

TLS chain troubleshooting is about whether the server presents a certificate path a client can build to a trusted root. A server certificate can be valid for the hostname and dates yet still fail clients because an intermediate is missing, duplicated incorrectly, or chained to an unexpected trust path.

Inspect exactly what the server presents

Use an external TLS client or scanner to capture the leaf and intermediates in presentation order. Compare the issuer of each certificate with the subject/key identifier of the next certificate in the intended chain.

Servers normally should not need to send the root CA certificate.

Check hostname and date separately

A chain error is different from a SAN/hostname mismatch or an expired certificate. Record all three dimensions so fixing the intermediate does not hide another failure.

Also check SNI: a server with multiple certificates may present a default certificate when tested by IP without the hostname.

Account for client trust differences

Modern browsers may fetch or cache intermediates that a minimal API client does not, so test with the clients that matter. An apparently healthy browser result can coexist with application failures if the server is not presenting a complete chain.

Legacy clients may also lack trust for newer roots or algorithms.

Install the provider-recommended full chain

Use the certificate plus correct intermediate bundle supplied by the CA/ACME client, reload the service, and retest externally. Monitor automated renewal to ensure the chain file updates with the certificate.

  • Capture presented chain.
  • Separate chain/hostname/date errors.
  • Test representative clients.
  • Retest after service reload.

Next step

Inspect the leaf certificate, intermediates, trust path, hostname and server configuration to find why one client accepts HTTPS while another rejects it.

See the DotMoose security approach

Keep reading

Related guides.

Content Security Policy rollout: build CSP from the resources a site really uses

Inventory scripts, styles, frames and connections, start with reporting, reduce unsafe allowances and enforce CSP only after normal user paths still work.

Read the guide

HSTS rollout planning: enable strict HTTPS without locking in a mistake

Stabilize HTTPS first, choose max-age carefully, cover subdomains deliberately and understand preload consequences before making HSTS hard to reverse.

Read the guide

HTTPS redirect mistakes: loops, chains and host changes that hurt a site

Find conflicting HTTP-to-HTTPS and hostname redirects across proxies, servers and applications, then reduce the path to one intentional canonical destination.

Read the guide

More security guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move