Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

issuer certificate invalid - firefox 36.0.4 - internal website

  • 2 antwurd
  • 3 hawwe dit probleem
  • 2 werjeftes
  • Lêste antwurd fan tgood69

tgood69
tgood69
more options

I have a few internal web servers that are used to manage networking equipment. These web sites get this error.

"Secure Connection Failed

An error occurred during a connection to XXX. Issuer certificate is invalid. (Error code: sec_error_ca_cert_invalid)"

I have added exceptions. did not change the symptom.

If I revert to an older version of FF I have no problems.

Obviously I would like to continue using FF but more and more of the things i do on my internal network are no longer working wth FF. It seems every update breaks something else i used to be able to do.

Getting VERY old and Ive about had it. Please fix this.

I have a few internal web servers that are used to manage networking equipment. These web sites get this error. "Secure Connection Failed An error occurred during a connection to XXX. Issuer certificate is invalid. (Error code: sec_error_ca_cert_invalid)" I have added exceptions. did not change the symptom. If I revert to an older version of FF I have no problems. Obviously I would like to continue using FF but more and more of the things i do on my internal network are no longer working wth FF. It seems every update breaks something else i used to be able to do. Getting VERY old and Ive about had it. Please fix this.

Bewurke troch tgood69 op

Alle antwurden (2)

guigs
guigs
more options

Hi tgood69, It is quite possible that the network machines are running into this issue because of the new CA guidelines mentioned below:

tgood69
tgood69 Fraacheigener
more options

guigs2 said

Hi tgood69, It is quite possible that the network machines are running into this issue because of the new CA guidelines mentioned below:

yay.. a policy... intended to break things...

Pretty much done with FF then. I have a JOB to do and when one of my tools makes my job MUCH more difficult. Then that tool needs to be thrown away.