Why does Firefox keep disabling the KEEPER add on?

Add-ons
1

Good morning, I have an annoying issue and do not know where else to go for an answer.
Firefox keeps disabling the Keeper Password Manager add-on every couple of days.
How do I keep this from happening?

2

I’m not sure what’s happening here. I can’t think of a reason why Firefox itself would repeatedly disable an add-on. To help debug the issue, I have a few questions for you:

  1. When Keeper is disabled, does Firefox display any messages about why the add-on was disabled?
  2. Do you have any other add-ons installed? If so, do they also get disabled or is it just this one add-on?
  3. What OS (+ version) are you using?
  4. What version of Firefox are you using?
  5. What version of the Keeper Password Manager add-on are you using?
    To check, navigate to about:addons, click Keeper in the list of add-ons, and look for the “Version” field near the bottom of the page.
  6. What is the add-on’s Extension ID?
    You can find this by navigating to about:debugging#/runtime/this-firefox, looking for the Keeper Password Manager in the list, and then finding the “Extension ID” row in it’s table.
3

John Holbrook jphmah1105@gmail.com 15 May 2025, 15:44 (18 hours ago)

to Simeon, bcc: me

Thank you Simeon for your response.

I must apologise for my tardiness in responding, it has been a busy week for me.

The answers to your requested information are as follows:-

When the Add-on is disabled does Firefox display any message

Keeper Password Manager & Digital Vault App could not be verified for use in Firefox and has been disabled.

Other Add-Ons

No other add-ons installed.

Firefox Version 138.0.1 (32 Bit) 20250414091429

Windows 10

2025-05 Cumulative Update for Windows 10 Version 22H2 for x86-based Systems (KB5058379)

Keeper Version 17.7.1 Last update 08 May 2025

Extension ID KeeperFFStoreExtension@KeeperSecurityInc

I hope this is the information you require and it can shed a little light on the problem.

I will await your response

John H.

4

notes

That error message tells us that the XPI file’s signature validation check is failing. The XPI file is the thing you download from AMO to install the extension. The signature is how we verify that the extension file you have on disk was is approved by Mozilla for distribution. Unfortunately that message doesn’t tell us why the check failed.

Was the version number a typo? The latest version of Keeper published on AMO is 17.1.1. For reference, the last updated date here is just the date that the current version of the add-on was installed.

The extension file on disk may be corrupt. Have you tried uninstalleing re-installing the add-on from AMO? If not, please try that.

5

G’day, Simeon,
Once again, thank you for your response.
To answer your queries:-

  1. Yes, the Keeper Version Number was a typo on my part, and it is:- 17.1.1
  2. The extension file on my disk may well have been corrupt, as it was reloaded at the time I started this contact with you.
    For your information, the add-on has not been disabled by the system since then (this always seems to happen when trying to locate a bug).
    The installed Firefox Version is now 138.0.4

I am now running 3 extensions:-

  1. Grammarly: AI Writing & Grammar Checker App
  2. Keeper Password Manager & Digital Vault
  3. System theme - Auto Extension ID:- default-theme@mozilla.org. (I don’t know where this came from; it just appeared in the list of Add-ons.

On each occasion that the add-on was disabled, the only way to reload it was to use the delete extension function in Firefox and close down Firefox, reboot Firefox, which would sometimes trigger the uploading of a new version of Firefox, then reinstall the Keeper add-on.

Simeon, what are your thoughts now, seeing that since the last reboot, things have been running without a glitch?

I await your response.
John H.

6

“System theme” is the default theme that ships with Firefox.

On each occasion that the add-on was disabled, the only way to reload it was to use the delete extension function in Firefox and close down Firefox, reboot Firefox … then reinstall the Keeper add-on.

That’s good to know In that case it wasn’t just disabled, it was blocked. That’s the behavior I expected from a signature verification failure. Since you indicated that you and to remove the add-on, re-install it from AMO, and that you still encountered the verification issue suggests that Firefox may have cached a corrupt version of the add-on’s CRX file. Also, since you haven’t seen it recently that suggests that either the cached version got replaced or that a Firefox update fixed the issue that cased the verification failure.

In either case, it sounds like you’re back in a good state. I’d say keep an eye out for any more odd behavior, but that you’re (hopefully) back to being trouble free.

7

Thank you, Simeon, for your attention to this matter. Your explanations have been invaluable in reassuring me regarding the problem I was having with the add-on.
I think we can now mark the issue as closed.
Thank you for your time.helping me resolve my problem

Best regards,
John Holbrook