![avast certificate error thunderbird avast certificate error thunderbird](https://blog.itgs-solutions.ch/wp-content/uploads/2019/04/avast_settings.png)
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.
#AVAST CERTIFICATE ERROR THUNDERBIRD INSTALL#
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. My server admins later determined that the Service SSL Cert needed to be replaced by the newest AlphaSSL wildcard certificate generated in August. I had generated the new wildcard cert via AlphaSSL a while ago (August). On the other hand, if you see that the certificate is owned by '', then run away as fast as you can.
![avast certificate error thunderbird avast certificate error thunderbird](https://d1ka0itfguscri.cloudfront.net/Lh/2021/05/31/13/15/crhwIoVhrd2/preview.jpg)
So once you confirm the exception, you'll be OK for 1 or 2 years. 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. The downside to this is that all certificates appear to be signed by avast Web/Mail Shield Root and can make things confusing at first glance when a SSL certificate is out of date. Therefore, Thunderbird complains that you are trying to install a certificate that might not be the proper one. I ended up generating an AlphaSSL certificate for my primary domain and installing that on the primary domain account, but the error still happened.