Firefox Community Forum

All of my addons are disabled and won't re-enable!

They all say "addon name" could not be verified for use in Nightly and has been disabled. See attachment clipboard00.jpg

If I try to install an addon from the recommended extensions settings (for example "return youtube dislike ") I get a message bubble stating "The Addon downloaded from this site could not be installed because it appears to be corrupt. {OK!}" See attachment clipboard01.jpg

The message above about addons appearing to be corrupt happens if I go to any of my current addon pages and try to redownload them.

Firefox says versions earlier than 115.13 will be impacted by the certificate expiration. I've updated to 115.21 My add-ons are still disabled. https://support.mozilla.org/en-US/kb/root-certificate-expiration

It seems many don't know or haven't noticed but merely running an esr branch (rather than a developer edition) will also give you the option to enable add-ons with expired certifications via about:config.

Anyway, the "legit" way isn't working.

Some quite strange questions, which I'm not sure to which category it belongs to, While I use last FF on my main machine, I have another machine that still use firefox 56.0.2 since I like some of the addons there that never been remade/updated to newer FF versions,

It worked fine for years but suddenly all of the addons are disabled no matter what I've tried to do, Using backup, reinstall, about:config and setting xpinstall.signatures.required to false, you name it,

I was wondering if Mozilla pulled the plug on something or if some fixed date for things to expired has arrvied, As well as if there's a way to fix it in the settings/other means?

Some people said that Dev or Nighty edition can actually turn the xpinstall signatures to false while normal FF might have the option but won't actually do it, The problem is that I have no cluse which of their versions is equal to good old 56.0.2, Can anyone tell me?

Thx

Hi,

suddenly, all of add-ons have been disabled.

It is say that is an security problems,..., but all of them?? suddenly??

can you please provide some support/help?

I attach screenshoot with release and evidences disabled.

Tks

hi I would like ask if is any way manually to update Root Certificate for my old firefox 88 .My extension ublock stop working today .I try to this but not works in my firefox .

about:config xpinstall.signatures.required to false extensions.langpacks.signatures.required to false

I do not want to update my firefox .There is any way to do somthing to works Add-Ons.

anyone know why I am getting this message all of a sudden,Installation aborted because the add-on appears to be corrupt.FoxyProxy, Wappalyzer and cookie manager all were red flagged , just happened!Cant download anyone of these The OS is Kali linux

Well, it's happened. I am using the unbranded build specifically so that I do not have to have signed or verified extensions. But tonight my browser broke anyway because of the expiring CA TLS certs for the add-ons repository.

"One or more installed add-ons cannot be verified and have been disabled [Learn More]". If I click the [Learn More] button nothing happens. It just disappears.

And when I check: "uBlock Origin could not be verified for use in Nightly and has been disabled."

This should not be happening in the unbranded builds. I imagine it is happening in the custom Debian esr too. They're supposed to allow unsigned/unverified extensions/add-ons but now this apparently bug is happening.

To be clear, this was expected for normal Firefox releases with all normal extension signing stuff. But that was explicitly not supposed to be required for the unbranded builds. And so this is a bug.

I checked my add-ons in settings to see what was wrong as I noticed the icons were missing. Upon looking at the proper tab, everything "could not be verified" (including themes) even though everything was working perfectly within 24 hours prior to the issue arising. When trying to reinstall anything from the extension store, all I receive is a "this appears to be corrupt and thus will not install." Clicking the "more information" button on any/all affected add-ons reveals that everything is unsigned. How do I alleviate this?

YouTube Downloader

If you have a legitimate question related to a Mozilla product, please submit a question with details at /questions/new.

A non-profit I support suggested the "Give Freely" app. The extensions search in Firefox did not find the app. Is it known and trusted by Mozilla? It's privacy policy suggests it functions like most other apps: it collects all the data it can, and allows the third parties that support their functions to collect all the data they can. The third parties can do whatever they like with my data.

Thank you,

David Guth

locking as duplicate of /questions/148784 thread

I was using Video Download Helper to download some YouTube videos. Suddenly, it stopped this evening. The button would remain grey. I tried using another LinkedIn video, and it worked, but it did not work with any YouTube video links. I gained access after I got a license 2-3 weeks ago Any suggestion on what is happening with YouTube links

I did reach out to GitHub. They referred me to contact the Video downloader support team, which is not part of their development.

Your response Number 2 If you are referring to this Extension https://addons.mozilla.org/firefox/addon/video-downloadhelper/ Look on the left side for the Support site link in the more information panel. It leads to https://github.com/aclap-dev/video-downloadhelper/discussions

My question is addressed once again, "Third attempt?" Please give a direct reply. Firefox should have the contact information since you permitted it to be part of your browser extension.

Back to my original question posted here once again Recently, the video downloader helper stopped working with videos of YouTube links. The video downloader helper on the Firefox window is grey, meaning inactive. I tried using a video from a LinkedIn web page and was able to download it. Any suggestion? I recently purchased the license for a video downloader helper. Thanks Arvind [edited email from community support forum]

Dear Sir,

Firefox is not working with Rabby Wallet and Metamask extensions.

It does no pop-up the window to see the transaction and sign it. Firefox 134.0.1 (64-bit). Windows 10 Home.

On Metamask at least I can click on the pinned extension and see the window. However it´s not the expected behavior, because it should open the pop-up automatically. With Rabby wallet it is impossible to proceed, even clicking on the extension icon.

Please fix it.

duplicate of /questions/1486143 thread

Dear Sir,

Firefox is not working with Rabby Wallet and Metamask extensions.

It does no pop-up the window to see the transaction and sign it. Firefox 134.0.1 (64-bit). Windows 10 Home.

On Metamask at least I can click on the pinned extension and see the window. However it´s not the expected behavior, because it should open the pop-up automatically. With Rabby wallet it is impossible to proceed, even clicking on the extension icon.

Please fix it asap.

duplicate of /questions/1486143 thread

Dear Sir,

Firefox is not working with Rabby Wallet and Metamask extensions.

It does no pop-up the window to see the transaction and sign it. Firefox 134.0.1 (64-bit). Windows 10 Home.

On Metamask at least I can click on the pinned extension and see the window. However it´s not the expected behavior, because it should open the pop-up automatically. With Rabby wallet it is impossible to proceed, even clicking on the extension icon.

Please fix it.

Locking this thread, please continue here: [/questions/1486142]
Dear Sir,

Firefox is not working with Rabby Wallet and Metamask extensions.

It does no pop-up the window to see the transaction and sign it. Firefox 134.0.1 (64-bit). Windows 10 Home.

On Metamask at least I can click on the pinned extension and see the window. However it´s not the expected behavior, because it should open the pop-up automatically. With Rabby wallet it is impossible to proceed, even clicking on the extension icon.

Please fix it.