This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Stop addons being disabled when PC has the wrong date

  • 3 پاسخ
  • 1 has this problem
  • 9 views
  • آخرین پاسخ توسّط cor-el

more options

Hello, whenever I change the date on my PC ( which I do several times per week for experiments), all my addons get disabled, as the browser decides they are unsigned (as visible in the screenshot)

And there is no way to re-enable them - I have to search for them again, go to the download site, and download them again. Yet the browser knows perfectly well that the date is wrong - so it should not be very hard to stop him from disabling addons during a period of wrong date.

Furthermore - there should be an option to re-check the validity of (all) addons which were disabled with 1 click, without having to re-download them.

Hello, whenever I change the date on my PC ( which I do several times per week for experiments), all my addons get disabled, as the browser decides they are unsigned (as visible in the screenshot) And there is no way to re-enable them - I have to search for them again, go to the download site, and download them again. Yet the browser knows perfectly well that the date is wrong - so it should not be very hard to stop him from disabling addons during a period of wrong date. Furthermore - there should be an option to re-check the validity of (all) addons which were disabled with 1 click, without having to re-download them.
Attached screenshots

All Replies (3)

more options

Add-ons use certificates that are date sensitive. In other words, the certificates are only good during a specific period.

more options

I could have guessed this already, yet there should be a real option to avoid this problem, - either not to disable, when the browser knows perfectly well the date is wrong, or to allow quick reactivation.

more options

You can try to force a signature check with this code in the Browser Console.


Cu.import("resource://gre/modules/addons/XPIDatabase.jsm");
await XPIDatabase.verifySignatures();

You can enable the command line in the Browser Console via the main developer tools settings (Web Console -> cogwheel button (F1).

Modified by cor-el