Once the current cert (from August) was installed there, TB works properly when accessing my primary domain account. I didn't know where it was being referenced from on the server to be in that list, but apparently it was in the Services SSL area. When I selected to Browse Apache certificates, I found what I believe to be the expired certificate that is being retrieved by Thunderbird and MS Mail. I did some research and it seems that Avast is replacing SSL certificates with their own.
#Avast certificate error thunderbird how to
I couldn't find the expired wildcard cert in Manage SSL Hosts or in SSL Storage Manager, but I *could* still see it on the server in the list when I was viewing the page where you install an SSL certificate and clicked the Browse Certificates button to view existing certs on the server. I just did a fresh install of my OS, Installed Avast and Firefox after they were downloaded, I opened Firefox, and was getting certificate errors, I turned off Avast's web shield and the problem went away. How to fix your connection is not secure cerrorexpiredissuercertificate The certificate is not trusted because the. My server admins later determined that the Service SSL Cert needed to be replaced by the newest AlphaSSL wildcard certificate generated in August. The configuration related to must be corrected. Peer’s certificate has an invalid signature. When I tried to send emails I get the following message: Sending of the message failed. I had generated the new wildcard cert via AlphaSSL a while ago (August). I cannot send or receive emails through Thunderbird (78.2.2). What was strange is that I noticed the cert that TB was showing in its error window was a wildcard cert that also had the root domain listed on it. I ended up generating an AlphaSSL certificate for my primary domain and installing that on the primary domain account, but the error still happened.
0 kommentar(er)
