
I autostart BINARY2 now on system start (Hit WIN-R, type shell:startup and paste a “link” to the correct keepassxc.exe) and that seems to do the trick for me. (not sure what weird wrapper the first binary is). Somehow, in this case the proxy will probably try to talk to the wrong binary. If I start the former, I will get a key exchange failed error.

IF I directly start the latter binary, the Firefox extension is able to connect to the running keepassxc. The binary in the former directory is what is started when one starts keepassxc through the PortableApps menu. The latter is also the directory which contains the keepassxc-proxy.exe. I noted that there are actually 2 binaries:Ĭ:\Users\spaetz\bin\PortableApps\KeePassXCPortable\KeePassXCPortable.exe (248kb) andĬ:\Users\spaetz\bin\PortableApps\KeePassXCPortable\App\KeePassXC\KeePassXC.exe (7094kb) NO combination of options, deleting of keepassxc and/or the browser extension, deletion of registry entries, or using a fresh Firefox profile helped. When I turned off the use of a proxy in the keepassxc settings (Browser integration -> Advanced), starting Firefox actually also started a keepassxc instance automatically, however all I still got was a “key exchange failed” error. Turning on add-on debugging led to the same result and not more helpful information. However, trying to connect, all I got is a “key exchange failed” error. When I started Firefox, I got a running keepassxc-proxy.exe process as a Firefox child process. which pointed to a correct path “C:\Users\spaetz\bin\PortableApps\KeePassXCPortable\App\KeePassXC\keepassxc-proxy.exe”.



On my Windows work laptop I am using the PortableApps version. I am using the excellent KeepassXC on all my computers, it works on Windows (work-supplied laptop), Linux (home) and there are mobile clients too.
