X
Tap here to go to the mobile version of the site.

Support Forum

How do I enable an add-on that "could not be verified for use in Firefox Developer Edition and has been disabled"?

Posted

I am using a number of extensions that were unexpectedly disabled when Firefox decided to update itself. The most important that "could not be verified for use in Firefox Developer Edition and has been disabled" is Mult-account containers. This is the second time I will have lost my data if I can't do so.

This being the second time I have to ask: Is this the fault of running "Developer Edition" and should I switch to normal FF at this point? Are containers not ready for prime time? Clearly something is wrong if I can loose all of my (container) data twice in a week.

I am using a number of extensions that were unexpectedly disabled when Firefox decided to update itself. The most important that "could not be verified for use in Firefox Developer Edition and has been disabled" is Mult-account containers. This is the second time I will have lost my data if I can't do so. This being the second time I have to ask: Is this the fault of running "Developer Edition" and should I switch to normal FF at this point? Are containers not ready for prime time? Clearly something is wrong if I can loose all of my (container) data twice in a week.

Additional System Details

Installed Plug-ins

  • Shockwave Flash 32.0 r0

Application

  • User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:67.0) Gecko/20100101 Firefox/67.0

More Information

cor-el
  • Top 10 Contributor
  • Moderator
17530 solutions 158508 answers

This is a problem with an expired intermediate certificate that is used to verify signed extensions that causes extensions to get disabled. This is being worked on.

See also:

At 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.
Our team is actively working on a fix. We will update as soon as we have more information.
  • Bug 1548973 - (armagadd-on-2.0) All extensions disabled due to expiration of intermediate signing cert

(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
)

This is a problem with an expired intermediate certificate that is used to verify signed extensions that causes extensions to get disabled. This is being worked on. See also: *https://www.reddit.com/r/mozilla/comments/bkhjms/yes_firefox_has_disabled_many_extensions_no_its/ *https://discourse.mozilla.org/t/certificate-issue-causing-add-ons-to-be-disabled-or-fail-to-install/39047 <blockquote><pre>At 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. Our team is actively working on a fix. We will update as soon as we have more information.</pre></blockquote> *[https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Bug 1548973] - (armagadd-on-2.0) All extensions disabled due to expiration of intermediate signing cert (<i>please do not comment in bug reports<br>https://bugzilla.mozilla.org/page.cgi?id=etiquette.html</i>)

Question owner

cor-el said

This is a problem with an expired intermediate certificate that is used to verify signed extensions that causes extensions to get disabled. This is being worked on. See also:
At 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.
Our team is actively working on a fix. We will update as soon as we have more information.
  • Bug 1548973 - (armagadd-on-2.0) All extensions disabled due to expiration of intermediate signing cert

(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
)

The fix pushed out through normandy has re-enabled the extensions, but all of my data in containers and preferences have been lost again. Is this what I can expect out of using containers? Are Firefox add-ons expected to forever lose all data through the fault of someone forgetting to renew a certificate or is there a problem in the container add-on?

Again I ask, are containers not ready for prime time? Clearly something is wrong if I can loose all of my (container) data twice in a week.

''cor-el [[#answer-1218212|said]]'' <blockquote> This is a problem with an expired intermediate certificate that is used to verify signed extensions that causes extensions to get disabled. This is being worked on. See also: *https://www.reddit.com/r/mozilla/comments/bkhjms/yes_firefox_has_disabled_many_extensions_no_its/ *https://discourse.mozilla.org/t/certificate-issue-causing-add-ons-to-be-disabled-or-fail-to-install/39047 <blockquote><pre>At 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. Our team is actively working on a fix. We will update as soon as we have more information.</pre></blockquote> *[https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Bug 1548973] - (armagadd-on-2.0) All extensions disabled due to expiration of intermediate signing cert (<i>please do not comment in bug reports<br>https://bugzilla.mozilla.org/page.cgi?id=etiquette.html</i>) </blockquote> The fix pushed out through normandy has re-enabled the extensions, but all of my data in containers and preferences have been lost again. Is this what I can expect out of using containers? Are Firefox add-ons expected to forever lose all data through the fault of someone forgetting to renew a certificate or is there a problem in the container add-on? Again I ask, are containers not ready for prime time? Clearly something is wrong if I can loose all of my (container) data twice in a week.
Mom 0 solutions 2 answers

So no one responded to your question?

So no one responded to your question?
cor-el
  • Top 10 Contributor
  • Moderator
17530 solutions 158508 answers

The multi account container extension stores its data in local storage (indexedDB). When this extension is disabled or otherwise uninstalled then the extension will get a new UUID as stored in extensions.webextensions.uuid and that will make you lose container data stored previously (i.e. it doesn't find this old data).

There is this pref that you can set to true on the about:config page make extensions keep thier UUID and prevent losing this connection.

The multi account container extension stores its data in local storage (indexedDB). When this extension is disabled or otherwise uninstalled then the extension will get a new UUID as stored in extensions.webextensions.uuid and that will make you lose container data stored previously (i.e. it doesn't find this old data). There is this pref that you can set to true on the <b>about:config</b> page make extensions keep thier UUID and prevent losing this connection. *extensions.webextensions.keepUuidOnUninstall = true *https://support.mozilla.org/en-US/kb/about-config-editor-firefox
Mom 0 solutions 2 answers

I read in an earlier comment that doing this could be dangerous. Is that still the case?

I read in an earlier comment that doing this could be dangerous. Is that still the case?