Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

Learn More

What causes extension updating errors?

  • 7 답장
  • 3 이 문제를 만남
  • 1 보기
  • 최종 답변자: Baldape

more options

Today around 3pm Firefox told me there where some add-on updates available but I noticed most of them didn't download instead I was presented with an update failed error message. So I fixed by manually installing the updates. But it got me thinking whats the cause for these errors? Is caused when mozilla.org is having difficulties or some fluke in Firefox is unable to connect to the server what exactly? Does anyone have the answers to my question? Thanks ahead time if you do.

Today around 3pm Firefox told me there where some add-on updates available but I noticed most of them didn't download instead I was presented with an update failed error message. So I fixed by manually installing the updates. But it got me thinking whats the cause for these errors? Is caused when mozilla.org is having difficulties or some fluke in Firefox is unable to connect to the server what exactly? Does anyone have the answers to my question? Thanks ahead time if you do.

선택된 해결법

We've signed a few chosen add-ons on friday, as opening a way to the add-on signing feature.

Those signed versions had their version number bumped, appending a ".1-signed" to them. The purpose was to have the update checks detect a new version, and install those newly signed versions.

Signing the add-ons files changed their hashes, but the CDN cached a previous version of the file. Long story short, the files would eventually be served properly once the CDN got flushed, but that's why some of you had this hash mismatch issue.

However, in the meantime, we discovered that the add-on signing would cause some issues to older versions of Firefox (28 and below). We thus reverted the change, and that's why the versions that were seen as updates no longer are.

If you did install those signed versions, no problem, you don't need to downgrade or uninstall/reinstall them. We'll be resigning those add-ons in the future.

문맥에 따라 이 답변을 읽어주세요 👍 1

모든 댓글 (7)

more options

I'm getting errors, too. To try to investigate further:

  • I opened the Add-ons page to the Available Updates section
  • I opened the Browser Console (Developer menu), and clicked the Clear button at the top
  • On the Available Updates page, I clicked the "Update Now" button for NoScript
  • In the Browser Console, I see this:

1429936376222 addons.xpi WARN Download of https://addons.cdn.mozilla.net/user-media/addons/722/noscript_security_suite-2.6.9.22-sm+fn+fx.xpi failed: Downloaded file hash (0c6774cd5479a315253eb403c6a7c074658154630ac9c4bc481aa0aba6eb16a8) did not match provided hash (c12fd43da6db7a976518b3df6cbcf99ff6260d18554a87d0c13332b4c5417b6e)

But I don't know why the downloaded file doesn't match the expected file. I didn't spot anything on the forums (https://forums.mozilla.org/). Maybe it's just us??

more options

jscher2000 said

I'm getting errors, too. To try to investigate further:
  • I opened the Add-ons page to the Available Updates section
  • I opened the Browser Console (Developer menu), and clicked the Clear button at the top
  • On the Available Updates page, I clicked the "Update Now" button for NoScript
  • In the Browser Console, I see this:
1429936376222 addons.xpi WARN Download of https://addons.cdn.mozilla.net/user-media/addons/722/noscript_security_suite-2.6.9.22-sm+fn+fx.xpi failed: Downloaded file hash (0c6774cd5479a315253eb403c6a7c074658154630ac9c4bc481aa0aba6eb16a8) did not match provided hash (c12fd43da6db7a976518b3df6cbcf99ff6260d18554a87d0c13332b4c5417b6e) But I don't know why the downloaded file doesn't match the expected file. I didn't spot anything on the forums (https://forums.mozilla.org/). Maybe it's just us??

I noticed that you use Noscript so do I maybe it's a bug with that? Or perhaps the OS what operating system are you using?

more options

Do you have security software that might inspect and possibly modify or repack the XPI (ZIP) archive?

Boot the computer in Windows Safe mode with network support (press F8 on the boot screen) as a test to see if that helps.

more options

cor-el said

Do you have security software that might inspect and possibly modify or repack the XPI (ZIP) archive? Boot the computer in Windows Safe mode with network support (press F8 on the boot screen) as a test to see if that helps.

Well I had Eset Nod32 on my Netrunner OS (Linux) and I'm also running Firejail (sandbox) for Firefox, but I'm not sure if I installed FJ correctly.

more options

I just thought of one common thing about jscher2000 and myself and thats Noscript.

more options

선택된 해결법

We've signed a few chosen add-ons on friday, as opening a way to the add-on signing feature.

Those signed versions had their version number bumped, appending a ".1-signed" to them. The purpose was to have the update checks detect a new version, and install those newly signed versions.

Signing the add-ons files changed their hashes, but the CDN cached a previous version of the file. Long story short, the files would eventually be served properly once the CDN got flushed, but that's why some of you had this hash mismatch issue.

However, in the meantime, we discovered that the add-on signing would cause some issues to older versions of Firefox (28 and below). We thus reverted the change, and that's why the versions that were seen as updates no longer are.

If you did install those signed versions, no problem, you don't need to downgrade or uninstall/reinstall them. We'll be resigning those add-ons in the future.

more options

Mathieu Agopian said

We've signed a few chosen add-ons on friday, as opening a way to the add-on signing feature. Those signed versions had their version number bumped, appending a ".1-signed" to them. The purpose was to have the update checks detect a new version, and install those newly signed versions. Signing the add-ons files changed their hashes, but the CDN cached a previous version of the file. Long story short, the files would eventually be served properly once the CDN got flushed, but that's why some of you had this hash mismatch issue. However, in the meantime, we discovered that the add-on signing would cause some issues to older versions of Firefox (28 and below). We thus reverted the change, and that's why the versions that were seen as updates no longer are. If you did install those signed versions, no problem, you don't need to downgrade or uninstall/reinstall them. We'll be resigning those add-ons in the future.

I remember hearing about this earlier last week. Thanks this anwsers my question perfectly.