#275 LocalCDN could not be verified for use in Firefox and has been disabled

Closed
opened 1 week ago by nerdcore · 3 comments
nerdcore commented 1 week ago

Hello there,

Long-term user of LocalCDN here. About 5 minutes ago, the following happened while I was working: Firefox automatically disabled LocalCDN and displays an error message now stating that the add-on could not be verified.

The remaining add-ons (uBlock Origin, ViolentMonkey, Redirector etc.) work flawlessly and are not affected by this circumstance.

Any idea what might have happened? Thanks!

LocalCDN v2.6.1
Firefox 86.0b (win64-EME-free, en-US)
Windows 10 Enterprise LTSC 1809

Hello there, Long-term user of LocalCDN here. About 5 minutes ago, the following happened while I was working: Firefox automatically disabled LocalCDN and displays an error message now stating that the add-on could not be verified. The remaining add-ons (uBlock Origin, ViolentMonkey, Redirector etc.) work flawlessly and are not affected by this circumstance. Any idea what might have happened? Thanks! LocalCDN v2.6.1 Firefox 86.0b (win64-EME-free, en-US) Windows 10 Enterprise LTSC 1809
nobody added the
firefox-bug
label 1 week ago
nobody commented 1 week ago
Poster
Owner

Any idea what might have happened?

Yes, I had that myself a few months ago, but with other extensions. Ghacks has also reported about it in 2019.

This is a bug in Mozilla's signing system. The signing is classified as invalid and automatically disabled. This can affect only one, multiple or all extensions.

The article on Ghacks also lists temporary solutions, e.g. disable signing of extensions.

> Any idea what might have happened? Yes, I had that myself a few months ago, but with other extensions. [Ghacks has also reported about it in 2019](https://www.ghacks.net/2019/05/04/your-firefox-extensions-are-all-disabled-thats-a-bug/). This is a bug in Mozilla's signing system. The signing is classified as invalid and automatically disabled. This can affect only one, multiple or all extensions. The article on Ghacks also lists temporary solutions, e.g. disable signing of extensions.
nerdcore commented 1 week ago
Poster

Thanks for your quick reply and the reference to the Ghacks article! I was able to solve the problem by editing the extensions.json file. This was quite confusing for me, since Firefox Nightly and ESR on the same computer were not affected by this problem.

You are doing a great job with LocalCDN, please keep it up! ;)

Thanks for your quick reply and the reference to the Ghacks article! I was able to solve the problem by editing the extensions.json file. This was quite confusing for me, since Firefox Nightly and ESR on the same computer were not affected by this problem. You are doing a great job with LocalCDN, please keep it up! ;)
nobody commented 1 week ago
Poster
Owner

Glad to see you found a solution there. Yes, that is confusing if only the beta is affected. This probably depends on how it's handled internally in the browser or what the server response is.

It was very good that you created the issue, because it will help other people who are affected to find a solution directly 👍 👍

You are doing a great job with LocalCDN, please keep it up! ;)

Thank you very much 😊

Glad to see you found a solution there. Yes, that is confusing if only the beta is affected. This probably depends on how it's handled internally in the browser or what the server response is. It was very good that you created the issue, because it will help other people who are affected to find a solution directly 👍 👍 > You are doing a great job with LocalCDN, please keep it up! ;) Thank you very much 😊
nobody closed this issue 1 week ago
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.