Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

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.

Confirm Security Exception [hangs] self signed cert

  • 2 antwurd
  • 1 hat dit probleem
  • 2 werjeftes
  • Lêste antwurd fan Casey

joeywpg
joeywpg
more options

Hi there, I created a self signed certificate for use with sending and receiving emails. However, when I try to send or receive I get the following error message: "Unknown Identity" The certificate is not trusted because it hasn't been verified as issued by a trusted authority using a secure signature." When I click "Confirm Security Exception" it just hangs. On the server side the error is: fatal bad certificate. SSL alert number 42 any suggestions would be appreciated. Thanks

Hi there, I created a self signed certificate for use with sending and receiving emails. However, when I try to send or receive I get the following error message: "Unknown Identity" The certificate is not trusted because it hasn't been verified as issued by a trusted authority using a secure signature." When I click "Confirm Security Exception" it just hangs. On the server side the error is: fatal bad certificate. SSL alert number 42 any suggestions would be appreciated. Thanks

Alle antwurden (2)

Matt
Matt
  • Top 25 Contributor
  • Moderator
more options

self signed certificates are getting like the dodo finding anyone that will allow them.

You might try disabling OCSP on preferences and see if disabling the validity checking helps. it makes things less secure, but ask others to trust your certificates really is not all that secure anyway.

Casey
Casey
more options

Had the same problem but was able to fix it using the ip address instead of the hostname at the servername. FYI: I am using a Dovecot server with a self-signed certificate. After changing this you should do File -> Get New Messages for -> Imap server and confirm the security exception (that should work now). Going back to the inbox should prompt you for the password (as you have a "new" server now).

After that it worked fine for me (in Thunderbird 102).