Karlston Posted May 4, 2019 Share Posted May 4, 2019 Some Firefox users started to notice that installed browser extensions were all disabled in the web browser suddenly. Extensions would display "could not be verified for use in Firefox and has been disabled" messages in the add-ons manager of the browser. Firefox would display "One or more installed add-ons cannot be verified and have been disabled" at the top as a notification next to that. Affected extensions include LastPass, Ghostery, Download Manager (S3), Dark Mode, Honey, uBlock Origin, Greasemonkey, NoScript, and others. Only options provided were to find a replacement and to remove the extension in question; this left affected users puzzled. Was this some kind of preemptive strike against policy violation extensions? Mozilla did announce that it would enforce policies more strictly. The answer is no. Turns out, the issue is caused by a bug. If you read carefully, you notice that verification is the issue. A new thread on Bugzilla suggests that this has something to do with extension signing. Firefox marked addons due signing as unsupported, but doesn't allow re-downloads from AMO → All extensions disabled due to expiration of intermediate signing cert. All Firefox extensions need to be signed since Firefox 48 and Firefox ESR 52. Firefox will block the installation of extensions with invalid certificates (or none), and that is causing the issue on user systems. Related issues have been reported: some users cannot install extensions from Mozilla's official Add-ons repository. Users get "Download failed. Please check your connection" errors when they attempt to download any extension from the official repository. Solution Nightly, Dev and Android users may be able to disable signing of extensions; some users reported that this resolved the issue temporarily on their end. You need to set the preference xpinstall.signatures.required to false on about:config to disable signing. You could change the system date to the previous day to resolve it temporarily as well, but that can lead to other issues. The issue can only be resolved on Mozilla's end. The organization needs to renew the certificate or create a new one to resolve the issue. I'd expect Mozilla to do that soon as the issue is widespread and affecting lots of Firefox users. Users should not remove affected extensions from their installations; the issue will resolve itself once Mozilla fixes it. Source: Your Firefox extensions are all disabled? That's a bug! (gHacks - Martin Brinkmann) Poster's note: It's affecting my Firefox, most extensions are now disabled. Grrr... Link to comment Share on other sites More sharing options...
Edgar.Elooo Posted May 4, 2019 Share Posted May 4, 2019 Same here! Link to comment Share on other sites More sharing options...
xpkRAKE Posted May 4, 2019 Share Posted May 4, 2019 Very annoying, until they get the certificate fixed I am using the "unbranded" version.... https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded_Builds I didn`t want to use Nightly, so this can easily be unzipped right over the main install - it will suffice for now. Edit: One addon still isn`t working, not ideal at all....but setting back the clock did appear to work. Link to comment Share on other sites More sharing options...
ugatme Posted May 4, 2019 Share Posted May 4, 2019 Found a work around. Enter about:debugging and check Enable add-on debugging. Now click load temporary addons and add xpi file. |Sorry, you must download the xpi file first. Link to comment Share on other sites More sharing options...
steven36 Posted May 4, 2019 Share Posted May 4, 2019 Firefox disabled all add-ons because a certificate expired Many Firefox users around the world are browsing without their usual set of extensions after they suddenly stopped working earlier this evening. The event occurred as the clock rolled over on UTC (Coordinated Universal Time, aka GMT or Greenwich Mean Time), and impacted users quickly narrowed it down to "expiration of intermediate signing cert" -- as it's described on Mozilla's bug tracker. This same problem almost happened three years ago, but "armagadd-on" 2.0 has torn things up once again. In a statement provided to Engadget, Product Lead Kev Needham said: Quote We're sorry that there is currently an issue where existing and new add-ons are failing to run or be installed on Firefox. We know what the issue is and are working hard to restore add-on functionality to Firefox as soon as possible. We'll continue to provide updates via our Twitter channels. Please bear with us while we get the problem fixed. For now, there is at least one workaround, but it only applies if you're using the Firefox Developer or Nightly build. If you look under "about:config" (if you don't know what this is, you probably shouldn't try it) and set the "xpinstall.signatures.required" value to False, then your extensions will start working again. Update: If you're on another version of Firefox, there is a way to temporarily fix it, but you'll have to repeat it every time you reopen the browser. It involves enabling add-on debugging and manually loading each extension's .xpi file. More at r/Firefox, Bugzilla, Mozilla Source Everything still work fine in waterfox my main browser think goodness i also have.chromium for backup browser too!!! Link to comment Share on other sites More sharing options...
shamu726 Posted May 4, 2019 Share Posted May 4, 2019 I just turned my clock back 1 day.. it's not a big problem for me. 😁 Link to comment Share on other sites More sharing options...
steven36 Posted May 4, 2019 Share Posted May 4, 2019 12 minutes ago, shamu726 said: I just turned my clock back 1 day.. it's not a big problem for me. 😁 Shame Shame i do a lot remote uploading with Firefox were i need newer addons now i go t move all the sites into chromium Since Firefox copy chrome they not very much difference in using open source chromium except Firefox has DRM for legit streaming sites on Linux and open source chromium don't . Link to comment Share on other sites More sharing options...
shamu726 Posted May 4, 2019 Share Posted May 4, 2019 I'm sure they'll fix this soon since this affects lots of users. Link to comment Share on other sites More sharing options...
steven36 Posted May 4, 2019 Share Posted May 4, 2019 3 minutes ago, shamu726 said: I'm sure they'll fix this soon since this is affects lots of users. Today just is not my day the multi mirror site i use to remote upload is messed up too they having database errors i give up tell tomorrow hopefully they fix it too soon . 🤔 Link to comment Share on other sites More sharing options...
The AchieVer Posted May 4, 2019 Share Posted May 4, 2019 Firefox add-ons disabled en masse after Mozilla certificate issue Firefox users report having add-ons disabled, being unable to re-activate or (re)-install extensions. Image via u/deleted_redacted on Reddit An expired certificate on the Mozilla Add-ons infrastructure is disabling Firefox add-ons for millions of users, and is also preventing users from re-activating or (re-)installing extensions. The issue doesn't impact all Firefox users, but it impacted enough to trigger a massive surge of complaints on Twitter, Reddit, and other social media sites. At the time of writing, the issue is still impacting Firefox users. The browser maker has formally acknowledged the issue in an email to ZDNet, on Twitter, in a status page, and in a bug report. "We're sorry that there is currently an issue where existing and new add-ons are failing to run or be installed on Firefox," a Mozilla spokesperson said. "We know what the issue is and are working hard to restore add-on functionality to Firefox as soon as possible." "We'll continue to provide updates via our Twitter channels. Please bear with us while we get the problem fixed," the browser maker said: Users of all Firefox versions, old and new, and Stable and Nightly, are impacted. The issue also impacts the Tor Browser, which supports Firefox add-ons. For Firefox users that are currently impacted by this bug, there is no easy workaround that doesn't involve them switching to another browser --an operation most users are trying to avoid, as this would require porting all their tabs, history, and add-ons to a new browser, which is a very time-consuming operation. One possible way to resolve this issue, as recommended by many Firefox users, would be to turn system clocks before May 4, 12:00am UTC (the date at which the Mozilla certificate expired), but this would also break other apps running locally, and which depend on an accurate system clock. Today's outage is happening because all Firefox add-ons are digitally signed since the release of Firefox 48, in the summer of 2016. This mechanism was introduced to fight off malware distributors that were abusing Firefox add-ons; however, it indirectly centralized all add-ons management operations by tying all extensions to Mozilla's server infrastructure. Source Link to comment Share on other sites More sharing options...
Image via u/deleted_redacted on Reddit An expired certificate on the Mozilla Add-ons infrastructure is disabling Firefox add-ons for millions of users, and is also preventing users from re-activating or (re-)installing extensions. The issue doesn't impact all Firefox users, but it impacted enough to trigger a massive surge of complaints on Twitter, Reddit, and other social media sites. At the time of writing, the issue is still impacting Firefox users. The browser maker has formally acknowledged the issue in an email to ZDNet, on Twitter, in a status page, and in a bug report. "We're sorry that there is currently an issue where existing and new add-ons are failing to run or be installed on Firefox," a Mozilla spokesperson said. "We know what the issue is and are working hard to restore add-on functionality to Firefox as soon as possible." "We'll continue to provide updates via our Twitter channels. Please bear with us while we get the problem fixed," the browser maker said: Users of all Firefox versions, old and new, and Stable and Nightly, are impacted. The issue also impacts the Tor Browser, which supports Firefox add-ons. For Firefox users that are currently impacted by this bug, there is no easy workaround that doesn't involve them switching to another browser --an operation most users are trying to avoid, as this would require porting all their tabs, history, and add-ons to a new browser, which is a very time-consuming operation. One possible way to resolve this issue, as recommended by many Firefox users, would be to turn system clocks before May 4, 12:00am UTC (the date at which the Mozilla certificate expired), but this would also break other apps running locally, and which depend on an accurate system clock. Today's outage is happening because all Firefox add-ons are digitally signed since the release of Firefox 48, in the summer of 2016. This mechanism was introduced to fight off malware distributors that were abusing Firefox add-ons; however, it indirectly centralized all add-ons management operations by tying all extensions to Mozilla's server infrastructure. Source
mp68terr Posted May 4, 2019 Share Posted May 4, 2019 Not affected. Using several browsers; when a site is broken FF is launched as being the only one running without any extension Link to comment Share on other sites More sharing options...
akks-mtb Posted May 4, 2019 Share Posted May 4, 2019 Not affected, using Firefox 67 beta 16 x64 Link to comment Share on other sites More sharing options...
cosy Posted May 4, 2019 Share Posted May 4, 2019 I have not also been affected yet, but wonder that Mozilla can make an urgent update to correct this one Hopefully, we get one soon or else I'm also thinking of dumping this browser soon too Link to comment Share on other sites More sharing options...
steven36 Posted May 4, 2019 Share Posted May 4, 2019 3 minutes ago, cosy said: I have not also been affected yet, but wonder that Mozilla can make an urgent update to correct this one Hopefully, we get one soon or else I'm also thinking of dumping this browser soon too There working on fix but they don't know when it be ready Quote Firefox 🔥Verified account @firefox Replying to @maarten_jf There's a certificate issue in Firefox that's 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. https://mzl.la/2vzrPFC -GS Quote Firefox 🔥Verified account @firefox 39m39 minutes ago Hey Maarten, sorry, I can't give an ETA on the fix, but we are doing our best. -GS https://twitter.com/firefox/status/1124572025220206592 Link to comment Share on other sites More sharing options...
crypto Posted May 4, 2019 Share Posted May 4, 2019 updated: FF 66.0.4 RC3, fixed add ons issue http://ftp.mozilla.org/pub/firefox/candidates/66.0.4-candidates/build3/win64/en-US/Firefox%20Setup%2066.0.4.exe Link to comment Share on other sites More sharing options...
jerx Posted May 4, 2019 Share Posted May 4, 2019 1 hour ago, crypto said: just get FF 66.0.4, fixed some add ons issue http://ftp.mozilla.org/pub/firefox/candidates/66.0.4-candidates/build1/win64/en-US/Firefox Setup 66.0.4.exe cookie auto delele does not fix, solution : get older version 3.0.1 ublock RC version does not fix too, solution: get final version from mozilla yep, it works back to normal (adguard & idm ext is working again) Link to comment Share on other sites More sharing options...
exodius Posted May 4, 2019 Share Posted May 4, 2019 Not affected on Firefox 66.0.3 x86 Windows 10 Pro, but i get this issue on my Firefox Android 66.0.2 .Hmm... weird Link to comment Share on other sites More sharing options...
attacker Posted May 4, 2019 Share Posted May 4, 2019 all add-ons are disabled on firefox 66.0.3 ☹️ Link to comment Share on other sites More sharing options...
BimBamSmash Posted May 4, 2019 Share Posted May 4, 2019 Yeps. That evil yellow banner presented itself at my end earlier today. The way it had everything deactivated and barred reinstalls had me think I was hacked, malware-fied or something. I was so close on going for a fresh OS install and I cannot emphasize on how much I dislike that process. That is one nasty bug. Woke me up better than a gallon of coffee could. Link to comment Share on other sites More sharing options...
shamu726 Posted May 4, 2019 Share Posted May 4, 2019 Quote Update: 10:50 a.m. UTC / 01: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. See the latest updates here https://discourse.mozilla.org/t/certificate-issue-causing-add-ons-to-be-disabled-or-fail-to-install/39047 Link to comment Share on other sites More sharing options...
masterupc Posted May 4, 2019 Share Posted May 4, 2019 It's fixed right now... 10.10am (-5 gmt) Link to comment Share on other sites More sharing options...
The AchieVer Posted May 4, 2019 Share Posted May 4, 2019 Update Regarding Add-ons in Firefox Late on Friday May 3rd, we became aware of an issue with Firefox that prevented existing and new add-ons from running or being installed. We are very sorry for the inconvenience caused to people who use Firefox. Our team has identified and rolled-out a fix for all Firefox Desktop users on Release, Beta and Nightly. The fix will be automatically applied in the background within the next few hours. No active steps need to be taken to make add-ons work again. To provide this fix on short notice, we are using the Studies system. This system is enabled by default, and no action is needed unless Studies have been disabled. Firefox users can check if they have Studies enabled by going to: Firefox Options/Preferences -> Privacy & Security -> Allow Firefox to install and run studies (scroll down to find the setting) Studies can be disabled again after the add-ons have been re-enabled It may take up to six hours for the Study to be applied to Firefox. To check if the fix has been applied, you can enter “about:studies” in the location bar. If the fix is active, you’ll see “hotfix-update-xpi-signing-intermediate-bug-1548973” as follows: You may also see “hotfix-reset-xpi-verification-timestamp-1548973” listed, which is part of the fix and may be in the Active studies or Completed studiessection(s). We are working on a general fix that doesn’t use the Studies system and will keep this blog post updated accordingly. We’ll continue to provide updates on continued efforts on this post, and will share a more substantial update in the coming days. Source Link to comment Share on other sites More sharing options...
Administrator DKT27 Posted May 4, 2019 Administrator Share Posted May 4, 2019 They have fixed it. The article is posted by The AchieVer above. Many people on the internet are posting how only now do they understand how the internet feels without addons. Hopefully Mozilla does not make such mistakes again and this is an example for everyone out there. Link to comment Share on other sites More sharing options...
v3n0m Posted May 4, 2019 Share Posted May 4, 2019 Not affected. Link to comment Share on other sites More sharing options...
niosi Posted May 4, 2019 Share Posted May 4, 2019 in the afternoon everything is back to normal Link to comment Share on other sites More sharing options...
3175x175(CURRENT).thumb.jpg.b05acc060982b36f5891ba728e6d953c.jpg)
Recommended Posts
Archived
This topic is now archived and is closed to further replies.