all my add-ons no longer supported?
all of a sudden I am being told that none of my add-ons are no longer supported by FF?? what? some i have had for years. what happened in the last 30 minutes that things changed??
All Replies (4)
There is a problem with an expired intermediate certificate that is used to sign extensions. This is being worked on by the Add-ons team.
See:
- [/questions/1257928] Will the disabling of add-ons be fixed, or is it the new way?
- https://discourse.mozilla.org/t/certificate-issue-causing-add-ons-to-be-disabled-or-fail-to-install/39047
At about 6:10 PST we received a report that a certificate issue for Firefox is causing add-ons to stop working and add-on installs to fail. Our team is actively working on a fix. We will update as soon as we have more information.
- Bug 1548973 - (armagadd-on-2.0) All extensions disabled due to expiration of intermediate signing cert
(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html)
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.
wolfdad 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