extensions have stopped working. Up to date extensions have been mistakenly called legacy extensions. How do I fix this?
In the latest version of Firefox, my up to date extensions have been said to be legacy extensions which they are not. How do I fix this?
The only thing that may annoy Firefox is that since version 57 it is not the default browser. I use Firefox only as a backup browser to my main browser Pale Moon.
Toutes les réponses (5)
Hi sosabuddy, it's not a problem with Firefox not being the default browser.
A critical Add-on-related certificate expired (which obviously should not happen). As a result, all verifications for that certificate are failing, preventing many extensions from being used, updated, or installed.
The Add-ons team is working on a fix for this. Official updates are expected to be posted here:
Currently, the only workaround is to set your system clock back (for example, if your date is May 3, set to May 2; if your date is May 4, set to May 3). You might have to reinstall extensions after that, or maybe Firefox will detect the difference at your next shut down/restart. Changing the date may have other consequences, so I understand this option isn't ideal.
Mozilla has rolled-out a fix for this. The fix will be automatically applied in the background within the next few hours, you don’t need to take active steps.
In order to be able to provide this fix on short notice, they are using the Studies system. You can check if you have studies enabled
- Go to [=] > Options > Privacy & Security.
- Make sure Allow Firefox to install and run studies is check marked.
I you had it disabled, you can disable studies again after your add-ons have been re-enabled.
They are working on a general fix that doesn't need to rely on this and will keep you updated.
sosabuddy said
There was a Bug-A-Boo with a Certificate Expiration Date dealing with the Add-ons. There's a new FF Version with the main Fix, 66.0.4.
Mozilla Blog Post Update:
A Firefox release has been pushed — version 66.0.4 on Desktop and Android, and version 60.6.2 for ESR. This release repairs the certificate chain to re-enable web extensions, themes, search engines, and language packs that had been disabled (Bug 1549061).
There are remaining issues that we are actively working to resolve, but we wanted to get this fix out before Monday to lessen the impact of disabled add-ons before the start of the week. More information about the remaining issues can be found by clicking on the links to the release notes above.
(May 5, 16:25 EDT)
~Pj