Bug in latest Firefox 65 update blocks HTTPS websites

After the update, HTTPS websites have become inaccessible for users using certain antivirus software.
If you just updated your software to the latest Mozilla Firefox 65 Version and can’t access HTTPS websites, you are not alone. As has recently come to light; the new update is not compatible with all Anti-Virus software and blocks HTTPS Connections.
Daniel Puschina,

Firefox version 65 was intended to provide users with an improved browsing experience by providing simplified content blocking controls, WebP image support, more privacy setting options and AV1-format support. However upon installing, the Firefox 65 update seems to do the contrary. Users reported experiencing problems visiting HTTPS websites, which appear to clash with certain antivirus programs; such as Avast, AVG and Kaperasky. 

In these cases the users received the error notifications "Your connection is not secure" and “SEC_ERROR_UNKNOWN_ISSUER”; as all HTTPS Connections were mistakenly blocked by Firefox. Early troubleshooting strategies have surfaced online and involve either manually deactivating HTTPS scanning or authorizing Firefox to accept Windows certificates. The antivirus manufacturers have also started working on resolving the issue on their end. 

Mozilla itself has published a bug report protocol for the bug, but is yet to release an official statement on the problem; instead they pulled the brakes on the version 65 Rollout making it unclear when the issue will be resolved. 


static version load dynamic
Loading Comments
Comment on this article
Please share our article, every link counts!
> Notebook / Laptop Reviews and News > News > News Archive > Newsarchive 2019 02 > Bug in latest Firefox 65 update blocks HTTPS websites
Daniel Puschina, 2019-02- 5 (Update: 2019-02- 5)
Daniel Puschina
Daniel Puschina - Editor
I am the generation who made the first computer experiences in the 90s on a 386 with the 20MHz turbo key. It was a tightrope walk between the performance limit of my computer and the scarce pocket money, but the motivation to get the last bit of performance out of it was all the greater. With 2MB of RAM, squeezing a single kilobyte out of the config.sys file was absolutely decisive for "Game starts" or "Game does not start". From this point on I also started to get more and more involved with benchmark tests, performance comparisons and tuning of components on the hardware side, which made me a permanent visitor to the Notebookcheck site in the last years. So it's a great pleasure for me to be able to write and test actively for this site myself.