Reviews for KeePassXC-Browser
KeePassXC-Browser by KeePassXC Team
Review by Myster
Rated 2 out of 5
by Myster, 6 years agoJust doesn't work.
Behaviour is so random. Extension works for some sites, and completely fails for others (about 70% of the websites I browse).
The most frustrating thing, is that this green icon appears in the login field, but nothing happens when you press it.
To be noted, this is consistent whichever browser I use (FF or Chrome) and whichever OS I run (Windows 10 or Linux Mint).
I gave a KeepassXC and the browser extension a try because it looked promising, and the KeepassXC GUI is nicer to plain Keepass, but it seems I have no other option than revert to Keepass + RPC pluging + Kee browser extension.
Sad.
Behaviour is so random. Extension works for some sites, and completely fails for others (about 70% of the websites I browse).
The most frustrating thing, is that this green icon appears in the login field, but nothing happens when you press it.
To be noted, this is consistent whichever browser I use (FF or Chrome) and whichever OS I run (Windows 10 or Linux Mint).
I gave a KeepassXC and the browser extension a try because it looked promising, and the KeepassXC GUI is nicer to plain Keepass, but it seems I have no other option than revert to Keepass + RPC pluging + Kee browser extension.
Sad.
Developer response
posted 6 years agoThe green icon appears if your database is unlocked. It doesn't tell if you have credentials for the site or not. The popup shows an icon with a questionmark if credentials are found, and the same feature will be implemented to the Username field icon later.
If you have troubles for getting your credentials to the site, please ensure your entry URL's are correct. Sometimes pages use iframes from other subdomains for the login fields, so the safest best is to use https://example.com instead of https://loginpage.example.com. When a subdomain is removed from the entry URL it works as a wildcard, meaning https://example.com will match https://*.example.com and so on.
If you have troubles for getting your credentials to the site, please ensure your entry URL's are correct. Sometimes pages use iframes from other subdomains for the login fields, so the safest best is to use https://example.com instead of https://loginpage.example.com. When a subdomain is removed from the entry URL it works as a wildcard, meaning https://example.com will match https://*.example.com and so on.
744 reviews
- Rated 5 out of 5by Mark Andrew Gerads, 6 days ago
- Rated 5 out of 5by SilverAmd, 11 days ago
- Rated 5 out of 5by Firefox user 19902880, 13 days ago
- Rated 5 out of 5by Craig, 14 days ago
- Rated 5 out of 5by Firefox user 19882925, 25 days ago
- Rated 5 out of 5by Firefox user 18863959, a month ago
- Rated 1 out of 5by Firefox user 14868755, a month agoNot able to add connected database. Nothing happens when clicking the Connect Database button. Bazzite 43 (linux) NVIDIA edition, Firefox 149, KeePassXC 2.7.12
- Rated 4 out of 5by Saturnus, a month ago
- Rated 4 out of 5by Fokeu, 2 months ago
- Rated 5 out of 5by Firefox user 13156335, 2 months agoWorks fine on my Windows 10 Firefox, and in Firefox on my CachyOS Linux install.
- Rated 5 out of 5by Cangrejo, 3 months agoBest password manager ever.
I know this depends of Keepassxc development, but it would be nice if card info can be stored. - Rated 5 out of 5by elsenfox, 3 months ago
- Rated 2 out of 5by Firefox user 19733088, 3 months agoEigentlich gut, aber umständlich, funktioniert bei vielen Websites einfach mal gar nicht, das Felderkennungs-Tool zum Zuweisen ebenfalls nicht und kostet daher viel Zeit und Nerven in der Benutzung. Daher kann ich ebenso schnell und gut aus KeepassXC kopieren und einfügen und brauche mich nicht mit diesem AddOn herumschlagen; leider!
- Rated 1 out of 5by John Hills, 3 months agoThe addon randomly shows errors like "KeePassXC-Browser has encountered an error: Key exchange was not successful" which means absolutely nothing to the user and does not help solve the problem in any way. It is the same as showing a message "Error: There has been an error. You're unlucky, too bad for you."
Developer response
posted 3 months agoGitHub already has an issue about this. In short, there's no way to get details from the API why the key exchange / connection fails. I suggest you take a look at the most common error threads and our Troubleshooting Guide at GitHub. - Rated 5 out of 5by Lani, 4 months agoIt seems that the path for native-messaging-hosts is hardcoded.
I want to move the file located at [~/.mozilla/native-messaging-hosts/org.keepassxc.keepassxc_browser.json] to [xdg-directory :: ~/.config/mozilla], but it fails.
help me? - Rated 1 out of 5by Ethan, 4 months agoit doesn't work when the password is on another page after the email. it always puts the wrong password from another account without even asking which account. developers, add a dropdown to ask the user from which account to take the password, don't just put any random password from any random account in the database. changing any setting didn't fix this.
Developer response
posted 4 months agoFirst of all, this shouldn't happen. There's already a dropdown selector when filling usernames or password from multiple accounts. Selector from the popup works as well. There are some settings that try to fill the password automatically for the selected username. Disabling those should help. If not, please file an issue to GitHub, thanks. - Rated 5 out of 5by A1, 4 months ago
- Rated 5 out of 5by ProgramminCat, 4 months ago
- Rated 5 out of 5by Xol, 4 months ago
- Rated 5 out of 5by Firefox user 16478816, 5 months ago
- Rated 5 out of 5by Ryan Steed, 5 months ago
- Rated 5 out of 5by Firefox user 19642928, 5 months ago
- Rated 4 out of 5by Enunciate_Veggie, 5 months ago
- Rated 5 out of 5by Firefox user 13447327, 5 months ago