3 ms·

Ask HN: Anyone else having issues with NoScript on Firefox

4 points by yubblegum 2y ago

My instance of Firefox (116.0.3) just unceremoniously disabled NoScript and uBlock Origin. "Could not be verified ..". Then I went to reinstall them and on their extensions page am getting "Installation aborted because the add-on appears to be corrupt." Can anyone else verify this or is this just specially for me? TIA

deleted 2y ago
[deleted]
k1t 2y ago
On 14 March a root certificate (the resource used to prove an add-on was approved by Mozilla) will expire, meaning Firefox users on versions older than 128 (or ESR 115) will not be able to use their add-ons. We want developers to be aware of this in case some of your users are on older versions of Firefox that may be impacted. https://blog.mozilla.org/addons/2025/03/10/root-certificate-will-expire-on-14-march-users-need-to-update-firefox-to-prevent-add-on-breakage/ https://blog.mozilla.org/addons/2025/03/10/root-certificate-... This link has more useful information - but the short answer is to update Firefox or switch to the latest ESR 115 if you're on an OS that isn't supported by the latest versions. https://support.mozilla.org/en-US/kb/root-certificate-expiration https://support.mozilla.org/en-US/kb/root-certificate-expira...
- yubblegum 2y ago
  thanks!
- probably_wrong 2y ago
  > We want developers to be aware of this in case some of your users are on older versions of Firefox that may be impacted. And yet the error doesn't say anything even remotely close to that, blaming the add-on instead. I found this thread when my add-ons suddenly stopped working without warning and without explanation. The help page didn't mention it either.
  - yubblegum 2y ago
    Agreed. Frankly stinks of a dark pattern.
abrefeld 2y ago
Also had this issue in LibreWolf on macOS. Updating the browser fixed things for me. brew install --force --cask librewolf
- yubblegum 2y ago
  thanks!