Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Unsigned plugin, dotEpub, won't show even though it says "preceed at your own risk."

  • 3 replies
  • 3 have this problem
  • 8 views
  • Last reply by sammydix

more options

I have the dotEpub plugin installed, and the extension page shows it as unsigned/untrusted. I've used it for a while and I trust it and there seems to be the "option" to proceed at my own risk (which for me is not a risk), but the plugin remains unseen no matter what. So I feel I'm being forced not to use something that I'm fine with using. So how do I "proceed at my own risk?"

I have the dotEpub plugin installed, and the extension page shows it as unsigned/untrusted. I've used it for a while and I trust it and there seems to be the "option" to proceed at my own risk (which for me is not a risk), but the plugin remains unseen no matter what. So I feel I'm being forced not to use something that I'm fine with using. So how do I "proceed at my own risk?"

All Replies (3)

more options

You are using Firefox 41. There is an option to disable the check, but it will be removed in Firefox 42. So you will have a limited time of being able to use unsigned add-ons in Firefox beta and release. You will need to use Nightly, Dev Edition or the soon to be released unbranded version of release to use unsigned add-ons.

It's better to check and make sure there are no updates to your add-ons (that might be signed already) and then bug the developers to sign their add-ons (a simple, automatic process)

more options

Chosen Solution

more options

Swarnava Sengupta said

You are using Firefox 41. There is an option to disable the check, but it will be removed in Firefox 42. So you will have a limited time of being able to use unsigned add-ons in Firefox beta and release. You will need to use Nightly, Dev Edition or the soon to be released unbranded version of release to use unsigned add-ons. It's better to check and make sure there are no updates to your add-ons (that might be signed already) and then bug the developers to sign their add-ons (a simple, automatic process)

Thank you. It would have been faster to mention exactly where that option was, but after a while, I found it. Appreciate the help.