![]() ![]() Note: This method can also be used to install add-ons from. Navigate the file dialog to your profile, then to the "extensions" folder inside. Next got to about:debugging and click Load Temporary Add-on. Go to ☰ > Help > Troubleshooting Information, then copy or make note of your "Profile folder" in the table. If you aren't sure which edition of Firefox you're on, it's probably Release, but you can see for yourself by heading to ☰ > Help > About Firefox.Įxtensions installed via Firefox's debugging tools are installed "temporarily", meaning they will be automatically disabled again on browser restart.Īll of your extensions currently reside in the "extensions" folder inside your profile folder. You can migrate to one of these editions using Firefox Sync or by telling it to use your original profile. There are some reports that you can disable signature enforcement on Linux or OSX regardless of Firefox ediiton. These editions are Firefox Developer Edition, Firefox Nightly, Extended Support Release, and the Unbranded builds. ![]() You can either 1: Temporarily load extensions, or, in some editions of Firefox, 2: Disable signature enforcement, telling your browser to trust all extensions. In the meantime, signing of new extensions is disabled until the fix is in place. PST: The team is currently testing a fix for this issue. We will update as soon as we have more information.ġ1:12 p.m. Here's the official acknowledgement from Mozilla on their Discourse:Ĭertificate issue causing add-ons to be disabled or fail to installĪt 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. In simpler terms, Firefox doesn't trust any add-ons right now. ![]() What this means is that every add-on signed by that certificate, which seems to be nearly all of them, will now be automatically disabled by Firefox as security measure. Nonetheless, I hope it's helpful.Ī few hours ago a security certificate that Mozilla used to sign Firefox add-ons expired. This is NOT an official Mozilla response. I do not work for Mozilla, and I am posting this thread entirely based on my own personal understanding of what's going on. Here's what's going on with your Add-ons being disabled, and how to work around the issue until its fixed.įirstly, as always, r/Firefox is not run by or affiliated with Mozilla. My add-ons page shows the add-on being 'deactivated' but they appear to be on and working. It is one of the mechanisms used to fix bug 1548973. This is a hotfix that updates an intermediate certificate used for signing add-ons. Hotfix-update-xpi-signing-intermediate-bug-1548973 When I click the "View Firefox studies" link in the Privacy & Security page I see one that: I have this enabled on mine and I don't think I'm using the beta or nightly builds. We are working on a general fix that doesn’t need to rely on this and will keep you updated. You can disable studies again after your add-ons have been re-enabled. You can check if you have studies enabled by going to Firefox Preferences -> Privacy & Security -> Allow Firefox to install and run studies. In order to be able to provide this fix on short notice, we are using the Studies system. The fix will be automatically applied in the background within the next few hours, you don’t need to take active steps. ![]() PDT: We rolled-out a fix for release, beta and nightly users on Desktop. to-be-disabled-or-fail-to-install/39047Ĭertificate issue causing add-ons to be disabled or fail to install:ġ2:50 p.m. Getting extensions back for everyone is going to require Mozilla to issue a patch.įrom that it sounds like AdBlocker Ultimate shouldn't be working for me but it is. Because the glitch stems from an underlying certificate, re-installing extensions won't work - if you try, you'll likely just be met with a different error message. Each extension is now being listed as a "legacy" extension, alongside a warning that it "could not be verified for use in Firefox and has been disabled." A ticket submitted to Mozilla's Bugzilla bug tracker first hit at around 5:40 PM Pacific, and suggests the sudden failure is due to a code signing certificate built into the browser that expired just after 5 PM (or midnight on May 4th in UTC time). Reports are pouring in of a glitch that has spontaneously disabled effectively all Firefox extensions. Did you just open Firefox only to find all of your extensions disabled and/or otherwise not working? You're not alone, and it's nothing you did. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |