Platform 18.0.1 (June 15, 2021). Please donate.
400+ real apps (41GB), Over 970 million downloads
New: CopyQ (June 17, 2021)
Has anyone tried integrating KeePassXC portable with Firefox Portable via the KeePassXC-Browser addon (https://addons.mozilla.org/en-US/firefox/addon/keepassxc-browser/)
I think there might be a problem with the fact that FF is portable and KeePassXC can't intercept it somehow?
Any ideas?
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
I can see "KeePassXCPortable\App\KeePassXC\keepassxc-proxy.exe" running when I launch Firefox so I guess some integration did occur, they're just not able to communicate with each other. I'm getting this error: "Cannot encrypt message or public key not found. Is native messaging or support for your browser enabled in KeePassXC?"
Seems nobody else use both portable... ;(
No ideas? Would be great to fix the issue.
Regards Jacek
An appeal to the more knowledgeable members of this forum - please, at least give us some directions what to look for. It's obviously not a user-specific issue, but something more global.
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
Seems obvious to me. The 'problem' with the Add-On is probably the most obvious one, i.e.. It has been written specifically to detect the KeePass database only if it can first detect an installed version of the KeePass program via the Windows system. It has no way of detecting that a portable version of the KeePass software exists and so makes no attempt to locate its database.
The correct approach would be to ask the Add-on developer if it is possible to adapt the add-on to access a KeePass database created by a Portable version. This would probably involve a settings option with which a User could specify the location of the database to be accessed.
No changes here? many many months pass through and that still does not work, right?
Regards Jacek
As stated above, you need to contact the publisher of the extension. It only works with the installed version by design. If you want otherwise, they need to change it.
With the newest version of chrome portable and KeePassXC it works!!!
Regards Jacek
Does it work with FirefoxPortable now as well now?
No news, unfortunately!
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....
*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).*
Same here: if I open keepassxc.exe NOT keepassxcportable.exe it works.
Also works for me. But then your Keepass is not really portable anymore.
It will save settings in %userprofile%\AppData\Local\KeePassXC instead of %PortableApps%\KeePassXCPortable\Data\settings.
For me it's ok. But you should be aware of this.
just wanted to report that keepassxc has a portable version on their website that works correctly.
i tried replacing the files under \PortableApps\KeePassXCPortable\App\KeePassXC but launching from KeePassXCPortable.exe the database can't connect.
hope devs can take a look at it....in the meantime i am using official version linked to the portableapps launcher.
The files within KeePassXCPortable\App\KeePassXC are the same files you just unzipped from the publisher's version.
I am using portable KeyPassXC with Chrome installed on the computer provided by my employer. I do get the same message about KeyPassXC not being able to connect through the Chrome extension. The executable is named KeePassXC.exe but it does not work.
What should I do?
Thanks a lot
Visit the Community page
Join our forums