What it means
Certificate authorities don't sign site certificates with their root directly. They use an intermediate certificate, and the server is expected to send it along with your own certificate so the browser can follow the chain up to a root it trusts. Your server sends your certificate but not the intermediate, and the root store doesn't contain it either.
Why it matters
Some desktop browsers hide the problem by downloading the missing intermediate or remembering it from another site, so the site may look fine on your computer. Phones, older systems, apps, payment providers, monitoring tools and command-line clients usually can't, and they fail with a certificate error. The result is a site that works for some visitors and not for others, which is hard to track down.
How to fix it
- Download the chain or bundle file from your certificate authority. Automatic clients already save it,
usually as
fullchain.pem. - Point the web server at the full chain instead of the certificate alone. The order is your certificate first, then the intermediate.
- Reload the web server, and check every server or load balancer that serves the site.
nginx
Use ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; rather than cert.pem, then run
sudo nginx -s reload.
Apache
On Apache 2.4.8 and later, point SSLCertificateFile at the full chain file. Older versions need
SSLCertificateChainFile set to the intermediate.
Load balancers and CDNs
When you upload a certificate, paste the intermediate into the chain field as well as your certificate.
Check it worked
Run the SSL check again. The chain section should list your certificate followed by the intermediate, and the card should say "Trusted".