Reviews for KeePassXC-Browser
KeePassXC-Browser by KeePassXC Team
Review by Myster
Rated 2 out of 5
by Myster, 4 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 4 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.