Avatar for Username

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

The certificate is not trusted because no issuer chain was provided

yr.garciadiaz
yr.garciadiaz

There is an archived thread with this question however in the many replies there isn't an explanation as to why this error is thrown on some systems and not on others and only on FireFox and not on Safari, Chrome, IE, FireFox (on Mac). Not on all Windows systems this error shows up but it shows in some window systems and in all the Linux systems that I have tried. So, is this a problem on the server or is it a FireFox problem?

There is an archived thread with this question however in the many replies there isn't an explanation as to why this error is thrown on some systems and not on others and only on FireFox and not on Safari, Chrome, IE, FireFox (on Mac). Not on all Windows systems this error shows up but it shows in some window systems and in all the Linux systems that I have tried. So, is this a problem on the server or is it a FireFox problem?

Chosen solution

You can get this certificate is not trusted error if server doesn't send a required intermediate certificate.

Firefox automatically stores intermediate certificates that servers send in the Certificate Manager for future usage. If a server doesn't send a full certificate chain then you won't get an untrusted error when Firefox has stored missing intermediate certificates from visiting a server in the past that has send it, but you do get an untrusted error if this intermediate certificate isn't stored yet.

You can inspect the certificate chain via a site like this:

Read this answer in context 👍 3

All Replies (2)

cor-el
cor-el
  • Moderator

Chosen Solution

You can get this certificate is not trusted error if server doesn't send a required intermediate certificate.

Firefox automatically stores intermediate certificates that servers send in the Certificate Manager for future usage. If a server doesn't send a full certificate chain then you won't get an untrusted error when Firefox has stored missing intermediate certificates from visiting a server in the past that has send it, but you do get an untrusted error if this intermediate certificate isn't stored yet.

You can inspect the certificate chain via a site like this:

yr.garciadiaz
yr.garciadiaz Question owner

Thanks! That explains the seemly erratic behaviour I was seeing.