Are your Firefox extensions disabled? This is a bug!

Some Firefox users began to notice that the installed browser extensions were all disabled in the web browser. The extensions would display messages "could not be verified for use in Firefox and have been disabled" in the browser's add-on manager. Firefox would display "One or more installed add-ons can not be checked and have been disabled" at the top of the notification next to this notification.

The affected extensions include LastPass, Ghostery, Download Manager (S3), Dark Mode, Honey, Lock Origin, Greasemonkey, NoScript and others.

Only the options proposed were to find a replacement and delete the extension in question; This left the concerned users perplexed. Was there any kind of preemptive strike against extensions of policy violation? Mozilla has announced that it will enforce stricter rules.

The answer is no. It turns out that the problem is caused by a bug. If you read carefully, you will notice that the check is the problem. A new thread on Bugzilla suggests that this has something to do with the signing of extension.

The addons marked by Firefox as unsupported but not allowing downloads again from AMO → All extensions disabled due to expiration of the intermediate signing certificate.

All Firefox extensions must be signed from Firefox 48 and Firefox ESR 52. Firefox will block the installation of extensions with invalid certificates (or none), which poses a problem on user systems.

Related issues have been reported: Some users can not install extensions from the official Mozilla add-in repository. Users receive the "Failed to download. Check your connection" error when they try to download an extension from the official repository.

Solution

Nightly, Dev and Android users may be able to disable signature extensions; Some users reported that the problem was resolved temporarily. You must set the xpinstall.signatures.required preference to false on about: config to disable signing. You can also change the system date from the day before to resolve it temporarily, but this can cause other problems.

The problem can only be solved on the Mozilla side. The organization must renew the certificate or create a new one to solve the problem. I would expect Mozilla to do this quickly because the problem is widespread and affects many Firefox users.

Users should not delete affected extensions from their installations. the problem will be solved once Mozilla corrects it.

Publicity