Thunderbird 102.0 unable to open https://addons.thunderbird.net/; gives "Secure Connection Failed" error
Installed TB 102.0 (64bit). Trying to search for addons inside Thunderbird, from Addons TB tab (e.g. for Bidi add-on, which is presently not compatible with TB 102.0: https://addons.thunderbird.net/en-US/thunderbird/search/?q=bidi&appver=102.0&platform=WINNT). Instead Thunderbird gives the following message: "Secure connection failed. The page you are trying to view can not be shown because the authenticity of the received data could not be verified." with invitation to "Try again". No success. Running Win 10 21H1 (64bit OS), and have Avast AV (22.5.6015 (build 22.5.7263.730)), where Thunderbird is an approved App. I believe the very first time I tried to search for addons, TB 102 actually opened the addons search page, but the second time and all subsequent times it is giving the Secure Connection Failed error. Any suggestions for the cause? Thankyou in advance.
Выбранное решение
Due to Thunderbird 102.0 corrupting email messages, I have downgraded back to 91.11.0. However, I discovered that Avast Web Shield, and specifically its HTTPS scanning, was blocking Thunderbird from accessing https://addons.thunderbird.net/* files. Turning off HTTPS scanning solved the problem. However, adding https://addons.thunderbird.net/* to Avast's General / Exception list of websites also solved the problem, allowing me to keep HTTPS scanning enabled. The latter is my preferred solution at this time.
Прочитайте этот ответ в контексте 👍 0Все ответы (2)
PS I can open the same Thunderbird addons webpages in Firefox without problem.
Изменено
Выбранное решение
Due to Thunderbird 102.0 corrupting email messages, I have downgraded back to 91.11.0. However, I discovered that Avast Web Shield, and specifically its HTTPS scanning, was blocking Thunderbird from accessing https://addons.thunderbird.net/* files. Turning off HTTPS scanning solved the problem. However, adding https://addons.thunderbird.net/* to Avast's General / Exception list of websites also solved the problem, allowing me to keep HTTPS scanning enabled. The latter is my preferred solution at this time.
Изменено