Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting errors trying to pair firefox extension with keepassx w/keepasshttp #76

Closed
NitrOP7674 opened this issue Aug 13, 2024 · 1 comment

Comments

@NitrOP7674
Copy link

Everything was working perfectly until today. It may be that I recently made changes to my keepass database on linux (to add integration between keepassxc and their extension) or on my android device (to change a password), which I rarely do.

Now when I click on the extension icon, it pops up a "new key confirmation" dialog in keepass. When I name the key, it seems to work, but the next time I click on the extension, it does the same thing with a different key, and never will let the keys be exchanged.

Seems like the same symptoms as #55 but different browser and different integration, so could be unrelated.

I tried restarting firefox and keepassx.

I ran the debug console for the extension and initiated a password request, and got the following error:

Error: response is not valid
    search moz-extension://acb57da5-61f5-44e9-84a8-d1b46bafc01f/connect/keepass/keepass.js:218
    search moz-extension://acb57da5-61f5-44e9-84a8-d1b46bafc01f/connect/api.js:78
    submit moz-extension://acb57da5-61f5-44e9-84a8-d1b46bafc01f/data/cmd/index.js:236
    <anonymous> moz-extension://acb57da5-61f5-44e9-84a8-d1b46bafc01f/data/cmd/index.js:915
    async* moz-extension://acb57da5-61f5-44e9-84a8-d1b46bafc01f/data/cmd/index.js:921

I have v0.8.1 of the plugin, v1.8.4.2 of KeePassHttp, and KeePass v2.57, and Firefox 129.0. Let me know if you need any more information or would like me to try anything else. And thank you for making this excellent plugin!

@NitrOP7674
Copy link
Author

I was able to fix this by doing the "factory reset" in the extension's options -- in case anyone runs into this issue later and is searching for the solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant