Ask questionsKeePassXC-Browser, Firefox Add-On - message "Timeout or not connected to KeePassXC"
<!--- Provide a general summary of the issue in the title above -->
<!--- If you're describing a bug, tell us what should happen --> <!--- If you're suggesting a change/improvement, tell us how it should work --> KeePassXC-Browser add-on connects from Firefox
KeePassXC-Browser, Firefox Add-On - "Timeout or not connected to KeePassXC". Reload button does not seem to do anything.
Firefox is my primary browser. I think keepassxc-proxy is not running (from Firefox). For testing purposes, I checked Google Chrome (KeePassXC Browser Integration tab) and added the Chrome extension. Works fine in Chrome and keepassxc-proxy is running (after Chrome is opened but not from Firefox).
Results from pgrep -la keepassxc:
2789 keepassxc
3664 keepassxc-proxy chrome-extension://oboonakemofpalcgghocfoadofidjkkk/
The keepassxc-proxy process that runs is only after opening Google Chrome. It seems keepassxc-proxy is not running from Firefox.
Contents of ~/.mozilla/native-messaging-hosts/org.keepassxc.keepassxc-browser.json:
{
"allowed_extensions": [
"[email protected]"
],
"description": "KeePassXC integration with native messaging support",
"name": "org.keepassxc.keepassxc_browser",
"path": "/home/roy/Programs/AppImage/keepassxc/KeePassXC-2.3.3-x86_64.AppImage",
"type": "stdio"
}
Contents of ~/.config/google-chrome/NativeMessagingHosts/org.keepassxc.keepassxc-browser.json:
{
"allowed_origins": [
"chrome-extension://iopaggbpplllidnfmcghoonnokmjoicf/",
"chrome-extension://oboonakemofpalcgghocfoadofidjkkk/"
],
"description": "KeePassXC integration with native messaging support",
"name": "org.keepassxc.keepassxc_browser",
"path": "/home/roy/Programs/AppImage/keepassxc/KeePassXC-2.3.3-x86_64.AppImage",
"type": "stdio"
}
Paths are the same and match expected values from Troubleshooting Guide. Both json files (Firefox and Chrome) have the same rw-rw-r-- permissions for the same user.
I turned on debugging in Firefox but it is not logging anything to console.
Both Chrome and Firefox are checked under KeePassXC/Browser Integration tab.
Other steps taken:
Other possible items of interest:
<!--- If describing a bug, tell us what happens instead of the expected behavior --> <!--- If suggesting a change/improvement, explain the difference from the current behavior -->
<!--- Not obligatory, but suggest a fix/reason for the bug, --> <!--- or ideas how to implement the addition or change --> I have not been able to manually run keepassxc-proxy as suggested in the Troubleshooting Guide. I checked 'varjolintu's repo and other sources and wasn't able to do it. I don't think it can be done with the AppImage KeePassXC version but maybe I am mistaken.
Don't know if it is a permissions issue with Firefox?
<!--- Provide a link to a live example, or an unambiguous set of steps to --> <!--- reproduce this bug. Include code to reproduce, if relevant --> 1. 2. 3. 4.
<!--- How has this issue affected you? What are you trying to accomplish? --> <!--- Providing context helps us come up with a solution that is most useful in the real world -->
<!--- Paste debug info from Help → About here --> KeePassXC - Version 2.3.3 Revision: 0a155d8 Distribution: AppImage
Libraries:
Operating system: Ubuntu 16.04.4 LTS CPU architecture: x86_64 Kernel: linux 4.4.0-128-generic
Enabled extensions:
Firefox Version 60.0.2 (64-bit) Chrome Version 67.0.3396.99 (Official Build) (64-bit) KeePassXC-Browser Version 1.1.7 (both Chrome and Firefox)
Answer questions
royracer
Where would the keepassxc-proxy binary be?
The current path in the Firefox JSON file is: "path": "/home/roy/Programs/AppImage/keepassxc/KeePassXC-2.3.4-x86_64.AppImage",
What should the correct path be?
Note, the Chrome json file has the same path as above and is working.
I also don't need to use the AppImage at all. Legacy Http-Connector still works with Firefox.
Also, I can try the Ubuntu distribution or snap image. It was awhile ago, but if I remember correctly, I only switched to AppImage because an older version of KeePassXC said to upgrade as the older browser integration was being deprecated.
Related questions