Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Learn More

Multiple addons suddenly "could not be verified"?

  • 15 trả lời
  • 2 gặp vấn đề này
  • 86 lượt xem
  • Trả lời mới nhất được viết bởi powerllama

more options

Earlier tonight, with no warning or apparent cause, the vast majority of my browser extensions suddenly stopped working with a "could not be verified for use in Firefox" error message. These include some popular ones, such as Adblock Plus, which I installed from addons.mozilla.org and I'm pretty sure are properly signed.

I'm on FF 66.0.3 and have been since April 10th, and all of them had been working fine up until now. I wasn't installing or updating anything at the time when they stopped working. I typically use a VPN service to connect to the internet, but the problem persists even after I turned it off, so I don't think that caused it. I can't think of anything else that might be the cause.

Any info or ideas on how to fix this would be appreciated.

Earlier tonight, with no warning or apparent cause, the vast majority of my browser extensions suddenly stopped working with a "could not be verified for use in Firefox" error message. These include some popular ones, such as Adblock Plus, which I installed from addons.mozilla.org and I'm pretty sure are properly signed. I'm on FF 66.0.3 and have been since April 10th, and all of them had been working fine up until now. I wasn't installing or updating anything at the time when they stopped working. I typically use a VPN service to connect to the internet, but the problem persists even after I turned it off, so I don't think that caused it. I can't think of anything else that might be the cause. Any info or ideas on how to fix this would be appreciated.

Giải pháp được chọn

Looks like it's working again now.

Đọc câu trả lời này trong ngữ cảnh 👍 0

Tất cả các câu trả lời (15)

more options

I don't think forum volunteers yet know the cause or remedy for this problem. However, know that dozens of people are reporting the same thing in recent hours, so it may be due to a rolling update gone wrong.

more options

jscher2000 said

I don't think forum volunteers yet know the cause or remedy for this problem. However, know that dozens of people are reporting the same thing in recent hours, so it may be due to a rolling update gone wrong.

Yup, I saw those just after posting my own question, haha. At least I know it's not just me!

more options

As an interim update: The Add-ons team is working on a fix for this. It looks like a certificate used to sign many popular extensions expired. (The verification process checks that certificate.)

I don't know how soon re-signed versions of those extensions will become available, or whether another workaround will be discovered. We are all hoping to learn more soon.

more options

Giải pháp được chọn

Looks like it's working again now.

more options
more options

I am using FF 60.6.1ESR and the problem persists in it. My system has Oracle Linux 6.5 (which is based on RedHat 6.5) and the latest version of FF supported by this OS is 60.6.1ESR.

more options

karthikeyan.d said

I am using FF 60.6.1ESR and the problem persists in it. My system has Oracle Linux 6.5 (which is based on RedHat 6.5) and the latest version of FF supported by this OS is 60.6.1ESR.

The Mozilla blog says that a fix for the ESR version will be available soon :

  An update for ESR users will be available tomorrow. We’re also 
 working on a fix for older versions of Firefox, and will update 
 this post and on social media as we have more information. 
 (May 7, 15:37 EDT)
     - https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox/
more options
more options

cor-el said

Note that the current is 60.6.2.

Yes. However, since the system is my office laptop I usually install using the official Yum repository which is yet to provide 60.6.2. Once the fix is available in a newer version I'll try it by downloading it directly from the FF web site.

more options

This is happening to me again on Firefox version 69.

more options

Hi powerllama, what does your Add-ons page, Extensions panel, show? For example:

  • There is a message explaining that the extension could not be verified, either on the little tile or when you click the add-on name to view its detail page.
  • There is no message or explanation, but there is no Enable button or the button is inoperable/disabled/grayed.
  • Something else.
more options

Multiple extensions with the "could not be verified" label. uBlock Origin, 1Password X, and Stylus. I can delete and redownload them from addons.mozilla.org but then I think I'll lose my Stylus CSS edits.

more options

powerllama said

Multiple extensions with the "could not be verified" label.

Hmm, a frequently updated extension like uBlock Origin shouldn't have a problem any more. Are you on the current version (1.22.2) ?

Could you check your system clock to make sure it's not a problem with time travel? The certificate used for verification is valid between:

Friday, April 3, 2015 - Thursday, April 3, 2025


To trigger a re-verification sooner than the usual "every 24 hours," you can use this method to clear the time stamp for the last time Firefox last re-verified.

(A) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.

(B) In the search box above the list, type or paste xpi- and pause while the list is filtered

(C) Right-click the app.update.lastUpdateTime.xpi-signature-verification preference and click Reset on the context menu -- the numeric value will disappear and the preference will say it is now a "string".

The next time you exit and restart Firefox, the re-verification should be performed within about a minute.

Success?

more options

You can try to start Firefox once with the '-purgecaches' command line parameter.


You can check for problems with the extensions registry files in the profile folder.

Try to to reset the extensions registry and rename extensions.json (extensionsOLD.json) and rename/remove previously used extensions files like extensions.ini and extensions.sqlite when present and rename/remove compatibility.ini in the Firefox profile folder with Firefox closed.

New files will be created when required.

See "Corrupt extension files":

You can check for possible updates in case of issues.

  • click the cogwheel button (left of the Search bar) on the about:addons page to "Check for updates"

If this didn't help then rename/delete add-ons.json and possibly prefs.js in case there is a problem with preferences.

You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.

more options

Today, everything showed back up. Not sure what the hiccup was! I'll save these options for later if it happens again. Thanks for the help!