What it means
The chain your server sends leads to a trusted root, but something along the way fails verification. Typical causes are an intermediate that has expired or been replaced, a signature made with an algorithm browsers no longer accept such as SHA-1, a key that is too short, a certificate that wasn't issued for websites, or files from two different orders mixed together.
Why it matters
Browsers and apps treat a chain that doesn't verify like an untrusted one: visitors see a security warning and automated clients refuse to connect.
How to fix it
- Look at the other findings in the result. A weak signature or a weak key finding usually names the cause.
- Check the dates in the chain section. An intermediate whose date has passed has to be replaced with the current one from your authority.
- Download a fresh copy of your certificate and its chain from your authority, or renew the certificate if it was signed with an outdated algorithm.
- Install your certificate and the matching chain file together, in order, then reload the web server.
Let's Encrypt with certbot
sudo certbot renew --force-renewal issues a fresh certificate with the current chain; point the server at
fullchain.pem and reload it.
Check it worked
Run the SSL check again. The card should say "Trusted" and the chain section should show certificates whose dates are all current.