-
Notifications
You must be signed in to change notification settings - Fork 275
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
Latest version of KeePassHTTP does not work with latest keepass #389
Comments
same here |
It works, but wont display any dialog if it finds more than one login for one URL. Seems like changes to firefox, chrome, chromium, vivaldi, opera triggered this, as it works up to firefox esr 60.x, but does not with later firefox versions. same for chrome-based browsers: older versions work, but not the latest ones. Keepasshttp seems to fill in user and password, but never click on "OK". Selecting one entry (even if it is only one entry) explicitly makes it fill in user and password and then click "OK" for you. Browsers not working:
Browsers working:
|
when i start keepass .. it says that the plugin is not compatible and then it is not working .. but okay for me now .. i also switched to keepassxc |
Doesn't work on KeePass 2.43 + KeePassHttp 1.8.4.2 + Vivaldi 2.7.1628.33 |
Does not work for me on Arch Linux with Keepass 2.42.1 + KeePassHttp 1.8.4.2 "The following plugin is incomppatible with the current KeePass version: |
This software is not maintained anymore: https://wiki.archlinux.org/index.php/KeePass#KeePassHTTP_for_Keepass I solved it by migrating to keepassxc.
so just 'sudo pacman -S keepassxc'. Then enable the HTTP-API in the settings of keepassxc. Finally get the Chromium-Plugin. It looks the same like the keepasshttp-plugin. |
Hi all,
|
I migrated to KeepassXC because it's more stable. It also has the funtionality of KeepassHTTP as inbuilt feature. |
yeah me too and that's work so much better, the KeePassXC-browser work better too |
The latest version of KeePasshttp does not work with Keepass 2.41
Can you update it?
The text was updated successfully, but these errors were encountered: