Fix an incomplete certificate chain
A server has to send its own certificate and the intermediate certificates that link it to a root clients trust. When it leaves one out, clients that cannot find the missing piece reject the connection, even though the certificate itself is valid and in date.
Why it works in your browser and fails elsewhere
Browsers often hide this. Firefox preloads the intermediates of publicly trusted CAs and builds the chain itself, and Certbot's docs warn that a server missing its chain fails in some browsers, some of the time. Other clients have no such help: curl fails on a chain with a missing intermediate, so an API client or a script can break while the site looks fine on your laptop. The curl Apple ships on macOS can pass where other builds fail, so test from another machine.
Confirm it
Ask the server for everything it sends:
openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null
Count the BEGIN CERTIFICATE blocks. A publicly trusted certificate needs at least one intermediate
after it, so a single block is the sign. Verify return code near the end reads 0 (ok)
for a complete chain, and for a missing intermediate names an error such as
unable to get local issuer certificate or unable to verify the first certificate. The
free checker shows the same from outside and reports a missing
intermediate as Urgent when it can fetch the intermediate itself, and as Down when it can't.
Fix it
Give the server one file holding its certificate followed by the intermediates, in that order.
- nginx:
ssl_certificatetakes the full chain. With certbot that isfullchain.pem. -
Apache 2.4.8 and later:
SSLCertificateFiletakesfullchain.pemtoo. Older Apache takescert.pemthere andchain.peminSSLCertificateChainFile, and needs both. -
A certificate downloaded from your CA: join the files, your certificate first:
cat example.com.crt intermediate.crt > fullchain.pem - A load balancer or CDN: it has its own field for the chain. Paste the intermediates there.
Then reload the service and confirm from outside. A new file changes nothing until the service reloads.
A deploy step that copies only cert.pem drops the chain on every renewal, so a chain that was fine
last cycle can break on this one.
How CertWatch catches this
CertWatch reads the chain the server sends on every hourly check, and fetching a missing intermediate elsewhere does not make it pass. CertWatch reports a missing intermediate as Urgent when it can fetch the intermediate itself, because it fails some clients now, and as Down when it can't. The alert names the finding and what to do about it, and a new certificate that brings the problem in alerts by its status even though the renewal itself went well.
Check a hostname now with the free checker, no account needed, or add it to CertWatch so every new certificate's chain is checked from outside.