Add-ons disabled on ESR >115.13+
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.
Chosen solution
By default, Firefox won't retry verification for 24 hours (source). Try toggling xpinstall.signatures.required back to true tomorrow and restarting using the "Clear startup cache..." button on the Troubleshooting Information page. (Use the Troubleshooting Information page to help fix Firefox issues)
Read this answer in context 👍 1All Replies (4)
neijyry said
toggling xpinstall.signatures.required to false is the workaround
Yopu should not have to do that with 115.13.0esr and later including 115.21.0esr.
You said you updated to 115.21.0esr, perhaps the version you were using did not meet the minimum requirements and the extensions were disabled. You then updated to Fx 115.21.0esr as did you restart Firefox after the update?
Setting that Preference to false makes you vulnerable as Extensions, malware and such that would have been blocked can now easily install in Firefox.
Chosen Solution
By default, Firefox won't retry verification for 24 hours (source). Try toggling xpinstall.signatures.required back to true tomorrow and restarting using the "Clear startup cache..." button on the Troubleshooting Information page. (Use the Troubleshooting Information page to help fix Firefox issues)
That seems to be it, thanks. I didn't need to clear the startup cache, nor toggle the preference since it let's you know when you're bypassing the checks, and that goes away when it gets the updated certificate.
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.