why you want to push your old user to chrome by block add-ons
Holidays back, I found my firefox disable by blocking all the add-ons. I try to downgrade firefox and so on and it didn't work. waste of time. you all had succed to chage me to chrome user since these years by updating to block most old add on. I tried my hard to stay. But finally today, I found it's silly dicision to stay only to find anthor not suitable add-on these year. I have to move on to chrome for stable add-ons . wasted me some time to switch to Chrome, but it worth. Bye the original developers for using your product these ten years and fuck the new developers for ruining it. and at the end , I can't figure it out ——Why you want to push your old user to chrome by block add-ons !!
Solution choisie
See also these threads about to add the certificate manually:
- /questions/1258208 plugins could not be verified firefox esr 52
- /questions/1258275 How do I re-enable the add-ons WITHOUT being forced to upgrade
Toutes les réponses (9)
Hey, this wasn't an update and it wasn't intentional. A critical certificate used in verifying add-on signatures expired, so you need a hotfix to install, enable, or update most add-ons. More info in this article:
Solution choisie
See also these threads about to add the certificate manually:
- /questions/1258208 plugins could not be verified firefox esr 52
- /questions/1258275 How do I re-enable the add-ons WITHOUT being forced to upgrade
cor-el said
See also these threads about to add the certificate manually:
- /questions/1258208 plugins could not be verified firefox esr 52
- /questions/1258275 How do I re-enable the add-ons WITHOUT being forced to upgrade
/questions/1258208 works for me. thanks
jscher2000 said
Hey, this wasn't an update and it wasn't intentional. A critical certificate used in verifying add-on signatures expired, so you need a hotfix to install, enable, or update most add-ons. More info in this article: Add-ons disabled or fail to install on Firefox
what you said on /questions/1258208 works for me. thanks. Overview
(1) Install the certificate the hotfix would have installed (2) Trigger Firefox to re-verify your extensions (3) Wait until it is back to normal
wish it won't happen again.
jscher2000 said
Hey, this wasn't an update and it wasn't intentional. A critical certificate used in verifying add-on signatures expired, so you need a hotfix to install, enable, or update most add-ons. More info in this article: Add-ons disabled or fail to install on Firefox
not update? doubt it . 10hours later I found another pc works for an hour then suddenly shutdown all add-on. feel connect with the firefox network, update or something. hate it so rude
jscher2000 said
Hey, this wasn't an update and it wasn't intentional. A critical certificate used in verifying add-on signatures expired, so you need a hotfix to install, enable, or update most add-ons. More info in this article: Add-ons disabled or fail to install on Firefox
not update? doubt it . 10hours later I found another pc works for an hour then suddenly shutdown all add-on. feel connect with the firefox network, update or something. hate it so rude
hateyoublockaddon said
jscher2000 saidHey, this wasn't an update and it wasn't intentional. A critical certificate used in verifying add-on signatures expired, so you need a hotfix to install, enable, or update most add-ons. More info in this article: Add-ons disabled or fail to install on Firefoxnot update? doubt it . 10hours later I found another pc works for an hour then suddenly shutdown all add-on. feel connect with the firefox network, update or something. hate it so rude
If you skim through the many threads, you'll see it affected users of Firefox 48, 52, 54, 56, and 65 as well as 66 and the Extended Support Release of Firefox 60.
The time factor is that Firefox will re-verify extension signatures every 24 hours. The first time it checked after midnight on May 4th (UTC time) is when the verification failed.
jscher2000 said
hateyoublockaddon saidjscher2000 saidHey, this wasn't an update and it wasn't intentional. A critical certificate used in verifying add-on signatures expired, so you need a hotfix to install, enable, or update most add-ons. More info in this article: Add-ons disabled or fail to install on Firefoxnot update? doubt it . 10hours later I found another pc works for an hour then suddenly shutdown all add-on. feel connect with the firefox network, update or something. hate it so rude
If you skim through the many threads, you'll see it affected users of Firefox 48, 52, 54, 56, and 65 as well as 66 and the Extended Support Release of Firefox 60.
The time factor is that Firefox will re-verify extension signatures every 24 hours. The first time it checked after midnight on May 4th (UTC time) is when the verification failed.
Yes, it affected my different computers' 52\56\60ESR version.I just didn't figure out why this event was triggered after an hour or some time connecting to the network. Ok, I guess I get it.
See also Mozilla Add-ons on Twitter: "The current plan is to push an update to update versions older than 64, but the current ETA is sometime Monday"