Integrate KeePassXC portable with Firefox Portable via the addon

I have the same problem here with Chrome Portable:

KeePassXC portable with Chrome Portable via the KeePassXC-Browser addon

Any ideas how that could work?

Regards Jacek

Seems nobody else use both portable... ;(

No ideas? Would be great to fix the issue.

Regards Jacek

The problem is, if you use both KeePassXC portable with chrome or firefox portable, you are not able to connect the datebase of keepass with the portable browser. You just get this error:

KeePassXC-Browser has encountered an error:
Timeout or not connected to KeePassXC

I already take a look in google to fix the issue, but nothing helps. Seems to be a problem when you use both programms as portable versions.
Hope it helps a little bit.

Regards Jacek

No changes here? many many months pass through and that still does not work, right?

Regards Jacek

With the newest version of chrome portable and KeePassXC it works!!!

Regards Jacek

I have the same problem too...

Is someone have make a test with KeePassXCPortable and a installed X-browser ?

As it did not work with both in portable version, I have tried with KeePassXCPortable and installed browser (Firefox) and it don't work too...

could you do the same test (and with other browsers installed), that would allow to advance
(...because maybe it's just a problem with the extension 'KeePassXC-Browser' and the portable versions...)

ty

Hi there, I had the problem that Portable Keepassxc (2.5.3) only ever led to a "Key Exchange failed" message. I have it solved for me now, perhaps it works for others. I posted an keepassxc issue at (https://github.com/keepassxreboot/keepassxc/issues/4348) but it was immediately closed as they don't want to be bothered with Portable-specific issues.

Initial Problem
Some things worked:
I had a registry key under "Computer\HKEY_CURRENT_USER\Software\Mozilla\NativeMessagingHosts\org.keepassxc.keepassxc_browser",
it pointed to the correct org.keepassxc.keepassxc_browser_firefox.json file
which pointed to a correct path "C:\Users\spaetz\bin\PortableApps\KeePassXCPortable\App\KeePassXC\keepassxc-proxy.exe"

When I started Firefox, I got a running keepassxc-proxy.exe process as a Firefox child process. However, trying to connect, all I got is a "key exchange failed" error. Turning on add-on debugging led to the same result and not more helpful information.
When I started keepassxc and turned off the use of a proxy, starting Firefox actually started a keepassxc process, however all I still got was a "key exchange failed" error.

NO combination of options, deleting of keepassxc and/or the broweser extension, deletion of registry entries, or using a fresh Firefox profile helped.

Possible Solution

I noted that there are actually 2 binaries:
BINARY1:
C:\Users\spaetz\bin\PortableApps\KeePassXCPortable\KeePassXCPortable.exe (248kb) and
BINARY2:
C:\Users\spaetz\bin\PortableApps\KeePassXCPortable\App\KeePassXC\KeePassXC.exe (7094kb)

The latter is also the directory which contains the keypassxc-proxy.exe. The binary in the former directory is what is started when one starts Keepassxc through the PortableApps menu.

IF I directly start the latter binary, the Firefox extension is able to connect to the running keepassxc. If I start the former, I will get a key exchange failed error. Somehow, in this case the proxy will probably try to talk to the wrong binary. (not sure what weird wrapper the first binary is).

I autostart BINARY2 now on system start and that seems to do the trick for me. I realize that this is not the fault of keepassxc, but given the multitude of reported errors and the unhelpful error message I think this might be of use for other users of the Portable Version. It might be useful on the wiki if confirmed by other users of the portable version on windows....