![Thunderbird logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2024-02-12-07-36-53-599028_1.png)
Security certificate crashes TB, maybe "server masking" related
For the past week, TB can't communicate with my website. It gives a security certificate error which I can't get rid of. My web hosts say that TB is expecting the certificate to refer to the name of my own server, but the certificate refers correctly to the "unmasked" server ie their server, and that I need to "simply" change the server names in TB to refer to their underlying server instead of my onw.
However I'm puzzled, because this is new. On June 13 the webhosts renewed the certificates, on June 14 Thunderbird 52.2 arrived (I think). So either TB is changed from last week, or the certificates are different from before.
I can't upload images of the error for some strange upload bug, but the ID on the certificate is:
- .34sp.com which is their own server
and TB is asking for a certificate for my server ie "Location mail.livenowlovenowhealnow.co.uk:143"
I can't succeed in "confirm security exception". I'd like to think I can just tweak some setting and it will work again, but why? Has something changed in TB52.2?
Many thanks
Andrew
தீர்வு தேர்ந்தெடுக்கப்பட்டது
I fixed the problem by reverting from Thunderbird 52.0 to Thunderbird 52.0. I don't know if 52.2 is somehow broken or if there was a failure of some kind during the automatic update - I guess I'll wait a couple of months, update to the next stable version, and see if the next version works.
Anyhow, if you have this problem, I'd try re-installing TB or reverting to an earlier version. Worked for me.
Read this answer in context 👍 1All Replies (1)
தீர்வு தேர்ந்தெடுக்கப்பட்டது
I fixed the problem by reverting from Thunderbird 52.0 to Thunderbird 52.0. I don't know if 52.2 is somehow broken or if there was a failure of some kind during the automatic update - I guess I'll wait a couple of months, update to the next stable version, and see if the next version works.
Anyhow, if you have this problem, I'd try re-installing TB or reverting to an earlier version. Worked for me.