Search Support

Beware of phishing attacks: Mozilla will never ask you to call a number or visit a non-Mozilla website. Please ignore such requests.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

You broke half of my addons on v56 and v54, studies fix is active, disabling singing did nothing. How to fix your failures?

  • 4 uphendule
  • 3 zinale nkinga
  • 18 views
  • Igcine ukuphendulwa ngu UsernameX

more options

Details: in title.

I sit on a super old version so you don't break my addons and you still manage to break them....

Isisombululo esikhethiwe

UPDATE: Firefox 66.0.4 and 60.6.2esr are now available with the new certificate needed to solve this problem. See: Update Firefox to the latest release.

Hi UsernameX, I don't know why the study hasn't come through. Maybe there was a change to how they work in a later version of Firefox, and it's not backwards compatible?

The study downloads a hotfix extension, and the hotfix extension installs a new certificate. So your options are:

(A) Wait for further official, supported solution(s) -- we don't know whether these will apply for non-current releases

(B) Download the hotfix extension directly and see whether it works (not officially supported)

(C) Install the certificate directly and then manually trigger re-verification (not officially supported)

For B and C:

B: Hotfix extension URL

I know this looks totally strange, but this is the one I have:

https://storage.googleapis.com/moz-fx-normandy-prod-addons/extensions/hotfix-update-xpi-intermediate%40mozilla.com-1.0.2-signed.xpi

("Normandy" is the system for managing studies.)

C: Manual certificate installation

I've posted detailed steps for Firefox 52 ESR users. The screens are a bit different, but you would use the same technique in newer versions of Firefox. See: https://support.mozilla.org/en-US/questions/1258165#answer-1218833

Funda le mpendulo ngokuhambisana nalesi sihloko 👍 1

All Replies (4)

more options

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

more options

I read that. I wrote in the title that the studies system is on and singing bugfix is active. I did notice now that besides the active study the other (*timestamp*) one is required yet hours passed and nothing changed. Also, there's no app.normandy.run_interval_seconds in my about config. I imagine the "general" fix won't help users refusing to get rid of most of their addons (by disabling old addons). So what can I do? Wait more?

more options

Isisombululo Esikhethiwe

UPDATE: Firefox 66.0.4 and 60.6.2esr are now available with the new certificate needed to solve this problem. See: Update Firefox to the latest release.

Hi UsernameX, I don't know why the study hasn't come through. Maybe there was a change to how they work in a later version of Firefox, and it's not backwards compatible?

The study downloads a hotfix extension, and the hotfix extension installs a new certificate. So your options are:

(A) Wait for further official, supported solution(s) -- we don't know whether these will apply for non-current releases

(B) Download the hotfix extension directly and see whether it works (not officially supported)

(C) Install the certificate directly and then manually trigger re-verification (not officially supported)

For B and C:

B: Hotfix extension URL

I know this looks totally strange, but this is the one I have:

https://storage.googleapis.com/moz-fx-normandy-prod-addons/extensions/hotfix-update-xpi-intermediate%40mozilla.com-1.0.2-signed.xpi

("Normandy" is the system for managing studies.)

C: Manual certificate installation

I've posted detailed steps for Firefox 52 ESR users. The screens are a bit different, but you would use the same technique in newer versions of Firefox. See: https://support.mozilla.org/en-US/questions/1258165#answer-1218833

Okulungisiwe ngu jscher2000

more options

I went with option C. It solved my problem both on v54 and v56 for most of the addons including all addons I actually cared about and actively used.

Thank you for your support jscher2000.