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

Support Forum

why you want to push your old user to chrome by block add-ons

Posted

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 !!

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 !!

Chosen solution

See also these threads about to add the certificate manually:

Read this answer in context 1
Quote

Additional System Details

Installed Plug-ins

  • Shockwave Flash 32.0 r0*

Application

  • User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0

More Information

jscher2000
  • Top 10 Contributor
8577 solutions 70123 answers

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

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]]
Was this helpful to you?
Quote
cor-el
  • Top 10 Contributor
  • Moderator
17343 solutions 156777 answers

Chosen Solution

See also these threads about to add the certificate manually:

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
Was this helpful to you? 1
Quote

Question owner

cor-el said

See also these threads about to add the certificate manually:

/questions/1258208 works for me. thanks

''cor-el [[#answer-1219120|said]]'' <blockquote> 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 </blockquote> [/questions/1258208] works for me. thanks
Was this helpful to you?
Quote

Question owner

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 [[#answer-1219100|said]]'' <blockquote> 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]] </blockquote> 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.
Was this helpful to you?
Quote

Question owner

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 [[#answer-1219100|said]]'' <blockquote> 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]] </blockquote> 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
Was this helpful to you?
Quote

Question owner

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 [[#answer-1219100|said]]'' <blockquote> 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]] </blockquote> 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
Was this helpful to you?
Quote
jscher2000
  • Top 10 Contributor
8577 solutions 70123 answers

Helpful Reply

hateyoublockaddon said

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

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.

''hateyoublockaddon [[#answer-1219379|said]]'' <blockquote> ''jscher2000 [[#answer-1219100|said]]'' <blockquote> 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]] </blockquote> 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 </blockquote> 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.
Was this helpful to you? 1
Quote

Question owner

jscher2000 said

hateyoublockaddon said
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

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.

''jscher2000 [[#answer-1219387|said]]'' <blockquote> ''hateyoublockaddon [[#answer-1219379|said]]'' <blockquote> ''jscher2000 [[#answer-1219100|said]]'' <blockquote> 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]] </blockquote> 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 </blockquote> 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. </blockquote> 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.
Was this helpful to you?
Quote
cor-el
  • Top 10 Contributor
  • Moderator
17343 solutions 156777 answers

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"

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" *https://twitter.com/mozamo/status/1124698401046577153
Was this helpful to you?
Quote
Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.