Avatar for Username

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Learn More

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Firefox recently began blocking my companies instance of SAP to launch another page. How can I bypass (Error code: sec_error_unknown_issuer)

  • 1 antwoord
  • 1 heeft dit probleem
  • 33 weergaven
  • Laatste antwoord van philipp

ntbinkle
ntbinkle
more options

This Connection is Untrusted

You have asked Firefox to connect securely to xxxx.xx.xxx, but we can't confirm that your connection is secure.

Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified. What Should I Do?

If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue.

xxxx.xx.xxx uses an invalid security certificate. The certificate is not trusted because no issuer chain was provided. (Error code: sec_error_unknown_issuer)

This Connection is Untrusted You have asked Firefox to connect securely to xxxx.xx.xxx, but we can't confirm that your connection is secure. Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified. What Should I Do? If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue. xxxx.xx.xxx uses an invalid security certificate. The certificate is not trusted because no issuer chain was provided. (Error code: sec_error_unknown_issuer)

Alle antwoorden (1)

philipp
philipp
  • Moderator
more options

hello ntbinkle, the issue with missing intermediary certificates ideally has to be solved by the server in question by properly implementing a certificate chain, linking the ssl-certificate for the url to the root certificate authority.

as a workaround, you might be able to manually import the missing intermediary certificate - therefore please attempt to add an exception on the bottom of the error page under i understand the risks & inspect the certificate (see the screenshot attached for instructions): which issuer information does the certificate contain?