![]() ![]() keepass.js:1307:25Ĭonnecting to native messaging host _browser keepass.js:1104:13Įrror 9: Key exchange was not successful. Is KeePassXC running? keepass.js:1187:13Įrror: No content script available for this tab. popup.htmlĮrror 7: Message encryption failed. If stylesheets are not yet loaded this may cause a flash of unstyled content. Layout was forced before the page was fully loaded. Use of nsIFile in content process is deprecated. But for some reason, one day, it stopped working. I know it was working with native messaging set to ~/.tb/tor-browser/Browser/TorBrowser/Data/Browser/.mozilla/native-messaging-hosts and the proxy custom pointing to my build. Tried every single workaround on the internet! I think keepassxc-proxy hang on starting. I built from source version 2.7 and 2.6.6 and I have the same problem. If you've lost the connection totally, the icon should be gray with and X (or gray with a lock icon if database is closed).I use Tor browser on Linux QubesOS. Notifications on why the filling doesn't work needs to be added so there's some indication to the user why nothing happens. Verify the page and entry URL again.įourth: Yes. Third: This means even after filling it doesn't regognize an entry from that page. ![]() If the site you're using is for example, the best entry URL for this kind of page is, (or just ). Second: Please use as simple URL's as possible in your entries. The next time this happens, check if the process is running. #KEEPASSXC WAIT SOFTWARE#This might be due to anti-virus software or some other process that interferes with it. If any of these issues are not solved, please open a ticket at GitHub.įirst: This sounds like the keepassxc-proxy that is transferring the messages between the extension and KeePassXC is shutdown. ![]() I am using KeepassXC 2.6.6 and browser extension version 1.7.9.1 #KEEPASSXC WAIT PASSWORD#Is it because it doesn't think I have a password for the domain? Has it lost the connection? Is there some invisible blocking me from clicking on the password icon? There is no way to tell, the addin simply doesn't respond. You are given no indication as to why the program cannot or will not fill the password fields. Third: When the auto-fill feature does work, it is frequently followed by an erroneous "your password has changed" prompt asking if you want to create a new entry for the site you literally just filled in.įourth: The user interface is minimalist to a fault. I would estimate that I can only successfully fill password forms on 5 to 10% of the websites I visit. Second: The password fill feature fails far more often than it works. It will occasionally disconnect and require you to restart KeepassXC before connecting again. It works extremely poorly for a number of reasons:įirst: It does not reliably connect to the KeepassXC program. This addon works by connecting to the KeepassXC program and filling login fields with the passwords from the Keepass vault. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |