Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Here's a general checklist for KeePassXC-Browser related connection issues:
1) After enabling Browser Integration and support for your browser
Depending on the operating system the
org.keepassxc.keepassxc_browser.json native messaging script file shoud be installed to these locations:
AppData\Local\keepassxc or to the KeePassXC directory if using portable version.
Also there should be a registry entry found in the following location(s):
If you use any other browser the configuration location can vary. In these cases the script file must be copied manually.
Some example Linux paths:
- Google Chrome Beta:
- Google Canary (Unstable):
2) Check the native messaging script file path and extension ID's
After finding the
org.keepassxc.keepassxc_browser.json check the
path variable inside it. It should point to the exact location to the KeePassXC binary. In Windows this variable can also exists without a path.
The extension ID under
allowed_origins should be
chrome-extension://oboonakemofpalcgghocfoadofidjkkk/ for Chromium-based browsers and
allowed_extensions for Firefox. There can be another ID seen with Chromium. This is the older version of the extension and it will be removed in the future from the script file.
With Chromium-based browsers you can check that the extension ID is the same with what is shown at the extensions page.
3) Check if keepassxc-proxy is launched and running
Connection between KeePassXC and the browser extension is managed by
keepassxc-proxy binary. Make sure this is up and running. If not try to start it manually. Under macOS the binary can be found inside the KeePassXC.app at
If the binary doesn't start on macOS, please check the binary linking with the following command:
otool -L /Applications/KeePassXC.app/Contents/MacOS/keepassxc-proxy
It should show the following for QtNetwork and QtCore frameworks:
It's possible to use KeePassXC without the proxy feature. This means the connection between the extension and KeePassXC is direct and KeePassXC must not be launched before the browser does it (at the startup or from the popup). This mean the extension cannot be connected to KeePassXC on-the-fly. Proxy can be disabled from the Advanced tab of Browser Integration settings. This is not the recommended setting.
4) Debug the extension itself
If everything else seems to be OK but you still have issues please try to debug the extension.
- Go to the extension page, check
backgroung pagelink after the
- Go to
Enable add-on debugging
- Find KeePassXC-Browser and click
Console tab should now show any error messages the extension writes. If you are a developer and know these things you can use the Sources tab and debug the extension and find the exact point where it fails.
Debug the content script
For debugging autocomplete, password generator, or anything else that interacts with the web page itself, content scripts must be debugged.
- Use the menu
View -> Developer -> Developer Toolsor with right mouse click on the page and select
- Go to
Sourcestab and use the double arrow on the top left of the Developer Tools to view
toptree and search for
- Use the menu
Tools -> Web Developer -> Debugger
- Go to
Sourcestab on the left and search for