can not connect to keepassXC from firefox/windows #2111

aombk · 2024-02-07T04:41:01Z

can not connect to keepassXC from firefox version 122 /windows 10
error: Key exchange was not successful.
tried what is mentioned in the troubleshooting guide

it works with edge and brave browsers

Debug info

[Error keepassxc-browser.js:980] KeePassXC-Browser - NotSupportedError: Operation is not supported
firefox downloaded from mozilla.org

KeePassXC - 2.76
KeePassXC-Browser - 1.8.12
Operating system: windows 10
Browser: firefox 122.0.1

varjolintu · 2024-02-07T05:25:18Z

Please report your findings based on the Troubleshooting Guide. That error seems strange.

aombk · 2024-02-08T02:29:16Z

I am not sure what you mean by that.
inside the folder: C:\Users{USER}\AppData\Local\KeePassXC are these files:

org.keepassxc.keepassxc_browser.json
org.keepassxc.keepassxc_browser_brave.json
org.keepassxc.keepassxc_browser_chrome.json
org.keepassxc.keepassxc_browser_chromium.json
org.keepassxc.keepassxc_browser_edge.json
org.keepassxc.keepassxc_browser_firefox.json
org.keepassxc.keepassxc_browser_tor-browser.json
org.keepassxc.keepassxc_browser_vivaldi.json

all chrome based browsers work and can connect
the files:

org.keepassxc.keepassxc_browser.json
org.keepassxc.keepassxc_browser_firefox.json
org.keepassxc.keepassxc_browser_tor-browser.json

contain this:

{
    "allowed_extensions": [
        "keepassxc-browser@keepassxc.org"
    ],
    "description": "KeePassXC integration with native messaging support",
    "name": "org.keepassxc.keepassxc_browser",
    "path": "C:\\Program Files\\KeePassXC\\keepassxc-proxy.exe",
    "type": "stdio"
}

the keepassxc-proxy.exe path is correct.

the registry contains the entries mentioned in the troubleshooter

i dont know what to do with process monitor

in firefox debugging i get these error messages:

KeePassXC-Browser: Connecting to native messaging host org.keepassxc.keepassxc_browser client.js:367:13
[Error ] KeePassXC-Browser - Failed to connect: Unknown error global.js:132:13
[Error ] KeePassXC-Browser - No content script available for this tab. global.js:132:13
[Error keepass.js:256] KeePassXC-Browser - 5: Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings. global.js:132:13
KeePassXC-Browser: Connecting to native messaging host org.keepassxc.keepassxc_browser client.js:367:13
[Error ] KeePassXC-Browser - Failed to connect: Unknown error global.js:132:13
[Error ] KeePassXC-Browser - No content script available for this tab. global.js:132:13
[Error ] KeePassXC-Browser - 9: Key exchange was not successful. global.js:132:13
[Error ] KeePassXC-Browser - No content script available for this tab. global.js:132:13
[Error keepass.js:256] KeePassXC-Browser - 5: Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings. global.js:132:13
[Error ] KeePassXC-Browser - No content script available for this tab. 2 global.js:132:13
[Error ] KeePassXC-Browser - Cannot send activated_tab message: Could not establish connection. Receiving end does not exist. 44 global.js:132:13
Uncaught (in promise) Error: Invalid tab ID: 581 undefined
[Error ] KeePassXC-Browser - Cannot send activated_tab message: Could not establish connection. Receiving end does not exist. 6 global.js:132:13
[Error keepass.js:256] KeePassXC-Browser - 5: Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings. global.js:132:13
KeePassXC-Browser: Connecting to native messaging host org.keepassxc.keepassxc_browser client.js:367:13
[Error ] KeePassXC-Browser - Failed to connect: Unknown error global.js:132:13
[Error ] KeePassXC-Browser - 9: Key exchange was not successful. global.js:132:13
KeePassXC-Browser: Connecting to native messaging host org.keepassxc.keepassxc_browser client.js:367:13
[Error ] KeePassXC-Browser - Failed to connect: Unknown error global.js:132:13
[Error ] KeePassXC-Browser - 9: Key exchange was not successful. global.js:132:13
KeePassXC-Browser: Connecting to native messaging host org.keepassxc.keepassxc_browser client.js:367:13
[Error ] KeePassXC-Browser - Failed to connect: Unknown error global.js:132:13
[Error ] KeePassXC-Browser - 9: Key exchange was not successful. global.js:132:13
[Error ] KeePassXC-Browser - Cannot send activated_tab message: Could not establish connection. Receiving end does not exist. global.js:132:13
[Error keepass.js:256] KeePassXC-Browser - 5: Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings. global.js:132:13
KeePassXC-Browser: Connecting to native messaging host org.keepassxc.keepassxc_browser client.js:367:13
[Error ] KeePassXC-Browser - Failed to connect: Unknown error global.js:132:13
[Error ] KeePassXC-Browser - 9: Key exchange was not successful. global.js:132:13
KeePassXC-Browser: Connecting to native messaging host org.keepassxc.keepassxc_browser client.js:367:13
[Error ] KeePassXC-Browser - Failed to connect: Unknown error global.js:132:13
[Error ] KeePassXC-Browser - 9: Key exchange was not successful. global.js:132:13
[Error ] KeePassXC-Browser - Cannot send activated_tab message: Could not establish connection. Receiving end does not exist.

also i dont know what to do with debugging keepassxc-browser.js in the firefox debugger

was that what you were asking for?

varjolintu · 2024-02-08T05:00:25Z

A couple of things to check:

Is the keepassxc-proxy.exe running?
What happens if you run it manually?
Have you tried to downgrade Firefox?

aombk · 2024-02-08T05:28:15Z

keepassxc-proxy.exe was running under the edge browser

if i run keepassxc-proxy.exe manually i get a blank window

and keepassxc-proxy.exe is now running under explorer.exe as well as under edge but firefox still cannot connect

no I havent tried downgrading, could try in the following days.

but why isnt it working? does it make any sense?

varjolintu · 2024-02-08T05:34:57Z

but why isnt it working? does it make any sense?

No it doesn't. This is why I suggested that you try to downgrade.

sakurawald · 2024-02-08T12:07:27Z

but why isnt it working? does it make any sense?

No it doesn't. This is why I suggested that you try to downgrade.

Please see this: #2113

aombk · 2024-02-10T13:48:47Z

ok so i tried a couple of older versions, and some portable ones, also tor browser. nothing seems to work. keepassxc-proxy.exe does not run with firefox. only with other chrome based browsers. what else can i try?

varjolintu · 2024-02-10T13:56:38Z

@aombk Can you paste the relevant registry entry here? You can also verify the path Firefox is trying to use with https://docs.microsoft.com/en-us/sysinternals/downloads/procmon

aombk · 2024-02-10T14:48:27Z

the key name is
HKEY_CURRENT_USER\SOFTWARE\Mozilla\NativeMessagingHosts\org.keepassxc.keepassxc_browser
and the value is
C:/Users/{USER}/AppData/Local/KeePassXC/org.keepassxc.keepassxc_browser.json

will check now with procmon

aombk · 2024-02-10T16:03:50Z

these are from procmon
i really dont know what to look for.

varjolintu · 2024-02-10T16:07:43Z

the key name is HKEY_CURRENT_USER\SOFTWARE\Mozilla\NativeMessagingHosts\org.keepassxc.keepassxc_browser and the value is C:/Users/{USER}/AppData/Local/KeePassXC/org.keepassxc.keepassxc_browser.json

will check now with procmon

Does this match with the registry entries with Chromium-based browsers?

aombk · 2024-02-10T16:36:52Z

yes, for edge its this:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Edge\NativeMessagingHosts\org.keepassxc.keepassxc_browser
C:/Users/{USER}/AppData/Local/KeePassXC/org.keepassxc.keepassxc_browser_edge.json

aombk · 2024-04-11T17:12:30Z

i would like to note that the issue is still not resolved

varjolintu · 2024-04-11T17:28:03Z

A couple of new points/questions:

Are you using some anti-virus or anti-malware software that could affect this?
Try disabling all other extensions and see if it solved the problem
Create a new temporary profile to Firefox and install the extension there, does it work?

aombk · 2024-04-11T19:24:47Z

I am using the microsoft windows built in security.
I disabled it and all firefox extensions and I also did a new firefox profile
but keepassXC browser plugin still could not connect to keepassxc software

varjolintu · 2024-04-12T03:47:41Z

Does re-enabling the "Update native messaging manifest files at startup" help?

aombk · 2024-04-12T09:10:21Z

I don't know where to re-enable that

varjolintu · 2024-04-12T09:53:20Z

I don't know where to re-enable that

Browser Integration -> Advaced. Accept the dialog with OK after doing that.

aombk · 2024-04-13T22:35:51Z

nope, it does not help unfortunately

varjolintu added the more info needed label Feb 7, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

can not connect to keepassXC from firefox/windows #2111

can not connect to keepassXC from firefox/windows #2111

aombk commented Feb 7, 2024

varjolintu commented Feb 7, 2024

aombk commented Feb 8, 2024

varjolintu commented Feb 8, 2024

aombk commented Feb 8, 2024

varjolintu commented Feb 8, 2024

sakurawald commented Feb 8, 2024

aombk commented Feb 10, 2024

varjolintu commented Feb 10, 2024

aombk commented Feb 10, 2024

aombk commented Feb 10, 2024

varjolintu commented Feb 10, 2024

aombk commented Feb 10, 2024

aombk commented Apr 11, 2024

varjolintu commented Apr 11, 2024

aombk commented Apr 11, 2024 •

edited

varjolintu commented Apr 12, 2024

aombk commented Apr 12, 2024

varjolintu commented Apr 12, 2024

aombk commented Apr 13, 2024

can not connect to keepassXC from firefox/windows #2111

can not connect to keepassXC from firefox/windows #2111

Comments

aombk commented Feb 7, 2024

Debug info

varjolintu commented Feb 7, 2024

aombk commented Feb 8, 2024

varjolintu commented Feb 8, 2024

aombk commented Feb 8, 2024

varjolintu commented Feb 8, 2024

sakurawald commented Feb 8, 2024

aombk commented Feb 10, 2024

varjolintu commented Feb 10, 2024

aombk commented Feb 10, 2024

aombk commented Feb 10, 2024

varjolintu commented Feb 10, 2024

aombk commented Feb 10, 2024

aombk commented Apr 11, 2024

varjolintu commented Apr 11, 2024

aombk commented Apr 11, 2024 • edited

varjolintu commented Apr 12, 2024

aombk commented Apr 12, 2024

varjolintu commented Apr 12, 2024

aombk commented Apr 13, 2024

aombk commented Apr 11, 2024 •

edited