kyrios
troubleshooting @1: "Depending on the operating system the org.keepassxc.keepassxc_browser.json native messaging script file shoud be installed to these locations: Chromium ~/.config/chromium/NativeMessagingHosts
Firefox: ~/.mozilla/native-messaging-hosts Vivaldi: ~/.config/vivaldi/NativeMessagingHosts "
The ,jsons are installed in those locations.
Troubleshooting #2) "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 keepassxc-browser@keepassxc.org under allowed_extensions for Firefox. "
{
"allowed_origins": [
"chrome-extension://pdffhmdngciaglkoonimfcmckehcpafo/",
"chrome-extension://oboonakemofpalcgghocfoadofidjkkk/"
],
"description": "KeePassXC integration with native messaging support",
"name": "org.keepassxc.keepassxc_browser",
"path": "/usr/bin/keepassxc-proxy",
"type": "stdio"
}
Check. All good.
3) Check if keepassxc-proxy is launched and running----------- yes it is
3.A) "If keepassxc-proxy is not launched and the extension still says it cannot connect, in Linux you can use strace to see where a browser tries to load the script file. Use Strace:sudo strace -f -p $(pgrep firefox) 2>&1 | grep keepass"
It's running. next command "The [sic] go to your browser, open the extension popup and press reload. That should trigger the Native Messaging to open the script file. You should see a line similar to this:
expected result: [pid 21992] openat(AT_FDCWD, "/home/varjolintu/.mozilla/native-messaging-hosts/org.keepassxc.keepassxc_browser.json", O_RDONLY <unfinished ...>"
actual result: "keychange was not successful"
step 4) debug
"Chromium-based browsers:
Use the menu View -> Developer -> Developer Tools or with right mouse click on the page and select Inspect
Go to Sources tab and use the double arrow on the top left of the Developer Tools to view Content scripts
Open top tree and search for KeePassXC-Browser. Open keepassxc-browser.js"
see the last sentence^^^^ it ends with find file. I found it. but I don't know how to debug it.
Ehhhh. come to speak of it I can't ATTACH a picture anymore in solus forum/flarum. not even with ad an image.
ugggghh
