This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

Add-ons/Extension Update: FireFox Extension Fixes Released! Updates for Versions 47-thru-65!

  • 3 biyano
  • 2 eza na bankokoso oyo
  • 2 views
  • Eyano yasuka ya James

more options

Updates – Last updated 14:35 PST May 14, 2019. We expect this to be our final update.

  • 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.
  • If you are running Firefox versions 57 – 60: Install This Extension to resolve the expired security certificate issue and re-enable extensions and themes.
  • If you are running Firefox versions 47 – 56: install This Extension to resolve the expired security certificate issue and re-enable extensions and themes.



Updates – Last Updated: 17:04 EDT May 9, 2019

A less technical blog post about the outage is also available. If you enabled telemetry to get the initial fix, we’re deleting all data collected since May 4. (May 9, 17:04 EDT)

Mozilla CTO Eric Rescorla posted a blog on the technical details of what went wrong last weekend.



Updates – Last Updated: 19:28 EDT May 8 2019

We’ve released Firefox 66.0.5 for Desktop and Android, and Firefox ESR 60.6.3, which include the permanent fix for re-enabling add-ons that were disabled starting on May 3rd. The initial, temporary fix that was deployed May 4th through the Studies system is replaced by these updates, and we recommend updating as soon as possible. Users who enabled Studies to receive the temporary fix, and have updated to the permanent fix, can now disable Studies if they desire.

For users who cannot update to the latest version of Firefox or Firefox ESR, we plan to distribute an update that automatically applies the fix to versions 52 through 60. This fix will also be available as a user-installable extension. For anyone still experiencing issues in versions 61 through 65, we plan to distribute a fix through a user-installable extension. These extensions will not require users to enable Studies, and we’ll provide an update when they are available.



"Updates – Last Updated: 11:51 EDT May 8 2019 (From Mozilla Blog)

Firefox 66.0.5 has been released, and we recommend that people update to that version if they continue to experience problems with extensions being disabled. You’ll get an update notification within 24 hours, or you can initiate an update manually.
An update to ESR 60.6.3 is also available as of May 8th. We’re continuing to work on a fix for older versions of Firefox, and will update this post and on social media as we have more information."



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)



"Last Updated: 00:54 EDT May 5 2019

Updates:

Some users are reporting that they do not have the “hotfix-update-xpi-signing-intermediate-bug-1548973” study active in “about:studies”.

Rather than using work-arounds, which can lead to issues later on, we strongly recommend that you continue to wait. If it’s possible for you to receive the hotfix, you should get it by 6am EDT, 24 hours after it was first released.

For everyone else, we are working to ship a more permanent solution. (May 5, 00:54 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)"

Quoted From This Mozilla Blog:

https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox/




~Pj (Yeah! My Extensions Are Back!)

Updates – Last updated 14:35 PST May 14, 2019. We expect this to be our final update. <B> * 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 [https://addons.mozilla.org/firefox/addon/disabled-add-on-fix-61-65/ This Extension] to resolve the expired security certificate issue and re-enable extensions and themes. * If you are running Firefox versions 57 – 60: Install [https://addons.mozilla.org/firefox/addon/disabled-add-on-fix-57-60/ This Extension] to resolve the expired security certificate issue and re-enable extensions and themes. * If you are running Firefox versions 47 – 56: install [https://addons.mozilla.org/en-US/firefox/addon/disabled-add-on-fix-52-56/ This Extension] to resolve the expired security certificate issue and re-enable extensions and themes.</B> <Hr> Updates – Last Updated: 17:04 EDT May 9, 2019 <B>A less [https://blog.mozilla.org/blog/2019/05/09/what-we-do-when-things-go-wrong/ technical blog post] about the outage is also available. If you enabled telemetry to get the initial fix, we’re deleting all data collected since May 4. (May 9, 17:04 EDT)<Br><Br> Mozilla CTO Eric Rescorla posted a blog on the [https://hacks.mozilla.org/2019/05/technical-details-on-the-recent-firefox-add-on-outage/ technical details of what went wrong] last weekend. </B> <Hr> Updates – Last Updated: 19:28 EDT May 8 2019 <B>We’ve released Firefox '''66.0.5''' for Desktop and Android, and Firefox ESR '''60.6.3''', which include the permanent fix for re-enabling add-ons that were disabled starting on May 3rd. The initial, temporary fix that was deployed May 4th through the '''Studies''' system is replaced by these updates, and we recommend updating as soon as possible. Users who enabled Studies to receive the temporary fix, and have updated to the permanent fix, '''can now disable Studies if they desire'''. For users who cannot update to the latest version of Firefox or Firefox ESR, <u><i>we plan to distribute an update that automatically applies the fix to versions 52 through 60.</i></u> This fix will also be available as a user-installable extension. For anyone still experiencing issues in versions 61 through 65, we plan to distribute a fix through a user-installable extension. These extensions will not require users to enable Studies, and we’ll provide an update when they are available. </B> <Hr> "Updates – Last Updated: 11:51 EDT May 8 2019 (From [https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox/ Mozilla Blog]) <B>Firefox 66.0.5 has been released, and we recommend that people update to that version if they continue to experience problems with extensions being disabled. You’ll get an update notification within 24 hours, or you can initiate an update manually. <Br> An update to ESR 60.6.3 is also available as of May 8th. We’re continuing to work on a fix for older versions of Firefox, and will update this post and on social media as we have more information." </B> <Hr> <B>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). <Br><Br> 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)</B> <Hr> "Last Updated: 00:54 EDT May 5 2019 Updates: <B>Some users are reporting that they do not have the “hotfix-update-xpi-signing-intermediate-bug-1548973” study active in “about:studies”. <Br><Br> Rather than using work-arounds, which can lead to issues later on, we strongly recommend that you continue to wait. If it’s possible for you to receive the hotfix, you should get it by 6am EDT, 24 hours after it was first released. <Br><Br> For everyone else, we are working to ship a more permanent solution. (May 5, 00:54 EDT)<Br><Br> 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)"</B> Quoted From This Mozilla Blog: https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox/ <Hr> ~Pj (Yeah! My Extensions Are Back!)

Ezalaki modifié na Pj

All Replies (3)

more options

The about:config setting is not effective in Firefox 66 on Windows/Mac/Linux. It works in:

  • Firefox Developer Edition
  • Firefox Nightly
  • Firefox 60 Extended Support Release (probably)
  • Firefox for Android

A Linux Mate user said it worked on theirs.


My current blurb:

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. So it's not your connection; it's everyone's connection.

The Add-ons team is working on a fix for this. Official updates are expected to be posted here:

https://discourse.mozilla.org/t/certificate-issue-causing-add-ons-to-be-disabled-or-fail-to-install/39047

Currently, the only workaround for the regular release of Firefox 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.

more options
more options

jscher2000 said

The about:config setting is not effective in Firefox 66 on Windows/Mac/Linux. It works in:
  • Firefox Developer Edition
  • Firefox Nightly
  • Firefox 60 Extended Support Release (probably)
  • Firefox for Android
A Linux Mate user said it worked on theirs.

Likely a third-party package build which can have their own changes and not a official Linux Firefox build from Mozilla