Sorry, the Add-ons team is working on a fix for this. It looks like a certificate used to sign many popular extensions expired. The verification process checks that certificate, and anything that doesn't pass is blocked.

I don't know how soon re-signed versions of those extensions will become available, or whether another workaround will be discovered. We are all hoping to learn more soon.

I'm not sure if it's an actual verification problem. Rather it might be a problem with the mozilla on this specific computer since my laptop doesn't have any issues with my addons and hasn't removed them.

It's not clear what triggers Firefox to detect this issue. Possibly when it checks for add-on updates?? We might not know until the whole thing is solved.

Is there anything I can check for or anything I can do? Again I mention that any time I try to reinstall the addons I get a connection failure issue message. Am I really having a connection issue?

Hi Trynagetafixhere, it is not your connection, it is something that happens in the background when trying to install, related to the expired certificate issue.

A possible workaround is to set your Windows system date back one day (for example, in the U.S., set it to May 2, 2019). This should allow extensions to be verified temporarily until the whole situation is resolved. I don't know if you need to exit/restart Firefox, or reinstall extensions. If you try it, please share your experience.

Aside from that, is the only thing I can really do to fix this is to wait? Also I would like to express my gratitude to you for helping me as much as you have and replying as quickly as you have.

One other workaround is to install the Developer Edition of Firefox and set it not to verify add-ons and then migrate your settings over, but that involves pre-release software and a lot of effort, so it's only going to aggravate most people...

Sorry I don't have more information. As you can see, the Add-ons team hasn't given us much yet: https://discourse.mozilla.org/t/certificate-issue-causing-add-ons-to-be-disabled-or-fail-to-install/39047

jscher2000 said

A possible workaround is to set your Windows system date back one day (for example, in the U.S., set it to May 2, 2019). This should allow extensions to be verified temporarily until the whole situation is resolved. I don't know if you need to exit/restart Firefox, or reinstall extensions. If you try it, please share your experience.

This worked for me. I'm getting some errors related to incorrect dates on some sites, but it's at least partially working now.

Mozilla has rolled-out a fix for this. 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, they are using the Studies system. You can check if you have studies enabled

1. Go to [=] > Options > Privacy & Security.
2. Make sure Allow Firefox to install and run studies is check marked.

I you had it disabled, you can disable studies again after your add-ons have been re-enabled.

They are working on a general fix that doesn't need to rely on this and will keep you updated.

Trynagetafixhere said

There was a Bug-A-Boo with a Certificate Expiration Date dealing with the Add-ons. There's a new FF Version with the main Fix, 66.0.4.

Mozilla Blog Post Update:
A Firefox release has been pushed — version 66.0.4 on Desktop and Android, and version 60.6.2 for ESR. This release repairs the certificate chain to re-enable web extensions, themes, search engines, and language packs that had been disabled (Bug 1549061).
There are remaining issues that we are actively working to resolve, but we wanted to get this fix out before Monday to lessen the impact of disabled add-ons before the start of the week. More information about the remaining issues can be found by clicking on the links to the release notes above.
(May 5, 16:25 EDT)

~Pj