Fail

One certificate in the bundle didn't sign the next

The short version

Rebuild the bundle from the certificates your certificate authority provides, leaf first.

What it means

In the bundle you decoded, one certificate wasn't signed by the certificate that should be its issuer, or a certificate doesn't belong to the chain at all. The names may still match: a certificate authority that renews its own intermediate keeps the name but changes the key, so an old intermediate looks right and verifies nothing.

Why it matters

A server that sends a broken chain makes browsers and mail servers fail to build a path to a trusted root. Some clients recover by fetching the right intermediate themselves; many don't, and phones, API clients and mail servers show a certificate error or refuse to connect. The problem often appears only after a renewal, when the new certificate is paired with the intermediate saved from last year.

How to fix it

  1. Download the intermediate certificates from your certificate authority for this exact certificate. Most authorities offer them on the order page or in the email with the certificate; don't reuse a bundle from an earlier order.
  2. Build the bundle leaf first: your certificate, then the intermediate that signed it, then any intermediate above that. Leave the root out.
  3. Remove any certificate that isn't part of this chain, such as an old intermediate or a certificate for another site.
  4. Install the new bundle on the server and reload it.

Check it worked

Paste the new bundle into the certificate decoder: every link should say it is signed by the next certificate. Then run the SSL checker against the site to confirm the server sends the fixed chain.