7 posts were merged into an existing topic: Almost every add-on is being shown as corrupt when installing them
Topic locked to keep clear for announcements, please discuss the issue here: Almost every add-on is being shown as corrupt when installing them
11:12 p.m. PST: The team is currently testing a fix for this issue. In the meantime, signing of new extensions is disabled until the fix is in place.
09:00 a.m. UTC/ 02:00 a.m. PDT: The team is still working on fixing and testing.
10:50 a.m. UTC / 03:50 a.m. PDT: We rolled-out a fix for release, beta and nightly users on Desktop. 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, we are using the Studies system. You can check if you have studies enabled by going to Firefox Preferences -> Privacy & Security -> Allow Firefox to install and run studies.
You can disable studies again after your add-ons have been re-enabled.
We are working on a general fix that doesn’t need to rely on this and will keep you updated.
Edited to add: Our blog has been updated with this information.
11:50 a.m. UTC / 04:50 a.m PDT: While we are working on updating and stabilizing systems, add-on submissions to AMO are currently held for approval. They will be automatically approved and signed once we get back to normal.
Hi folks. As of 8:54 p.m. PST, we have updated the post on the Add-ons Blog.
- We are not releasing permanent fixes tonight (Pacific).
- Some users are reporting that they do not have the “hotfix-update-xpi-signing-intermediate-bug-1548973” study active in “about:studies." If this is you, we are sorry for the inconvenience and encourage you to sit tight – an update is coming to you sometime soon via a deployed hotfix or a dot release. (May 4, 23:05 EDT)
- There are a number of work-arounds being discussed in the community. These are not recommended as they may conflict with fixes we are deploying. We’ll let you know when further updates are available that we recommend, and appreciate your patience. (May 4, 15:01 EDT)
9:20 p.m. UTC / 2:20 p.m. PDT:
We released Firefox 66.0.4 for Desktop and Android, as well as Firefox 60.6.2 ESR that re-enables extensions. For more information, please read the update on https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox Thank you for being patient with us! Thanks to everyone working on it!
13:33 EST / 20:33 UTC: Add-on signing has been re-enabled.
A new Firefox update has been released (version 66.0.5), which should address some additional issues regarding the certificate problem. Additionally, an update for ESR users is expected tomorrow.
As always, please check back on the blog post for updates: https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox
We have published two blog posts that you may want to read if you would like to learn more about what caused this incident and how Mozilla responded:
Technical Details on the Recent Firefox Add-on Outage by Firefox CTO Eric Rescorla
What we do when things go wrong by Joe Hildebrand, VP of Engineering, Firefox
Update for users of Firefox versions <60:
The official fix for 52 - 59 is still in testing. As these versions have not been supported for some time, it’s been considerably more complicated and has taken us more time to spin up the infrastructure to develop and test the fix.
If you are running Firefox 52 - 56, you can install this extension to fix the expired certificate issue and re-enable your extensions and themes: https://addons.mozilla.org/firefox/addon/disabled-add-on-fix-52-56/
If you are running Firefox 57 - 60, you can install this extension to fix the expired certificate issue and re-enable your extensions and themes: https://addons.mozilla.org/firefox/addon/disabled-add-on-fix-57-60/
If you are running Firefox versions 61 – 65 and 1) did not receive the deployed fix and 2) do not want to update to the current version (which includes the permanent fix): Install this extension to resolve the expired security certificate issue and re-enable extensions and themes.
This wraps up our planned deployments; if you continue to experience problems related to the expired certificate issue, please post on our forum and we will do our best to help you out.
A post was merged into an existing topic: Thread: Add-ons not working due to certificate expiration