Version 1.8.3 Breaks browser integration / autofill

[ongun-kanat]

Updating Keepass XC to 1.8.3 breaks browser integration. It seems like it is losing the handshake between the application and the extension. The issue exists on both Firefox and Chromium. I realized that there is a problem while using Firefox (my default browser) and then tested on Chromium. Chromium was working until I manually triggered the update to 1.8.3.

Expected Behavior

Autofill should work

Current Behavior

KeepassXC Browser is losing the connection between the application and the extension

Steps to Reproduce (for bugs)

1. Load the browser and visit any page. I used https://kskmse.de and https://hepsiburada.com
2. Wait the autofill icon show up shortly and then disappear
   a. On Firefox the icon turns into a lost connection one:
   
   b. On Chromium it stays as green
3. Triggering the form fill using the right-click context menu doesn't work.

Debug info

I use Windows 10 AMD64 with Keepass XC 2.7.3. Both browsers seem to generate similar logs in extension debug console.

Firefox v106.0.1:

KeePassXC-Browser: Connecting to native messaging host org.keepassxc.keepassxc_browser 2 [client.js:317:13](moz-extension://ebd6e01e-1a92-4433-b62e-13b953636469/background/client.js)
KeePassXC-Browser: Server public key: bKl+O5hcYtKrGqRQb5rJlzoiOGz2lWQDbdj/ndkEjn0= [keepass.js:449:17](moz-extension://ebd6e01e-1a92-4433-b62e-13b953636469/background/keepass.js)
[Error keepass.js:757] KeePassXC-Browser - 9: Key exchange was not successful. [global.js:178:13](moz-extension://ebd6e01e-1a92-4433-b62e-13b953636469/common/global.js)
[Error ] KeePassXC-Browser - Failed to connect: Unknown error [global.js:178:13](moz-extension://ebd6e01e-1a92-4433-b62e-13b953636469/common/global.js)
[Error init.js:66] KeePassXC-Browser - Cannot send activated_tab message: Could not establish connection. Receiving end does not exist. [global.js:178:13](moz-extension://ebd6e01e-1a92-4433-b62e-13b953636469/common/global.js)

Chromium v106.0.5249.119

[Error page.js:233] KeePassXC-Browser - Cannot send activated_tab message: Could not establish connection. Receiving end does not exist.

[varjolintu]

Does the same happen with KeePassXC 2.7.1?

[user858753257]

For me it's also on 2.7.1 (windows 10 with Edge)

[varjolintu]

Just tested this with Windows 10 where KeePassXC 2.7.1 was installed along with older Edge version. Updated KeePassXC to 2.7.3 and Edge to the latest version, and had no problems with it. Please see the Troubleshooting Guide and report your findings, thanks.

[MarkJaroski]

I'm also experiencing this behaviour.

oboonakemofpalcgghocfoadofidjkkk-1666713987336.log

Probably I should have edited the log file to keep just the last few dozen lines. You can see that the initial connection opening the database works, but after that any attempt to autofill generates errors like "No tab with id: x"

KeePassXC - 2.7.3
KeePassXC-Browser - 1.8.3
Operating System: Linux x86_64
Browser: Chrome

[obrowny]

I have the problem, it looses connection with the database regularly.
KeePassXC - 2.7.3
KeePassXC-Browser - 1.8.3
Operating system: Linux x86_64
Browser: Mozilla Firefox 105.0

[varjolintu]

See keepassxreboot/keepassxc#8634 for checking if the issue is with the socket.

[varjolintu]

@MarkJaroski Interesting. I haven't seen anything like that on my tests with multiple OS's. I highly suggest you shutdown KeePassXC and your browser, and also make sure keepassxc-proxy is killed before starting everything again. Also, are there popups visible on KeePassXC?

[MarkJaroski]

The advice here solved it for me:

keepassxreboot/keepassxc#8634 (comment)

Thanks @varjolintu for the link.

To quote the comment at the above link:

Make sure you have "Update native messaging manifests at startup" enabled in the advanced browser integration settings in KeePassXC and then restart KeePassXC.

[varjolintu]

Please try downgrading to 2.7.1 to narrow down the cause of the issue. Browsers should be restarted too.

[varjolintu]

I finally got this reproduced with 2.7.3. Investigating it. Your safest bet is to use 2.7.1 until this is fixed.

[Leseratte10]

I have this same issue in KeepassXC, on Linux using Chrome. The suggestion by MarkJaroski didn't work for me, downgrading KeepassXC to 2.7.1 fixes the issue.

[varjolintu]

The problem is fixed for 2.7.4, but it's necessary to use 2.7.1 meanwhile. Sorry for the trouble!

[MarkJaroski]

I have this same issue in KeepassXC, on Linux using Chrome. The suggestion by MarkJaroski didn't work for me, downgrading KeepassXC to 2.7.1 fixes the issue.

It stopped working for me too. It was only because of the restart.

[VeraSimon]

Was running into this issue with KeePassXC 2.7.3, KeePassXC-Browser 1.8.3, and Firefox 106.0.1 on Windows 10 Pro 21H1. Reverting KeePassXC-Browser to 1.8.2.2 seems to have fixed it.

[varjolintu]

@VeraSimon So KeePassXC 2.7.1 with extension 1.8.3 didn't work for you?

[VeraSimon]

@VeraSimon So KeePassXC 2.7.1 with extension 1.8.3 didn't work for you?

It was easier to revert the addon in the browser than juggle the version of KeePassXC I have installed on multiple machines and OSes, so I didn't try to revert the app. I also wasn't hitting any of the issues fixed in KeePassXC-Browser 1.8.3, so went with the quicker troubleshooting/break-fix. Just figured you might like to know that particular combo was working as expected.

[refugeindhamma]

Having the same problem here.

My debug info:

KeePassXC - 2.7.3
KeePassXC-Browser - 1.8.3
Operating system: Win64
Browser: Mozilla Firefox 106.0

Below is my debug log:

KeePassXC-Browser: Connecting to native messaging host org.keepassxc.keepassxc_browser [client.js:317:13](moz-extension://8050304e-1486-43f8-ab0b-c6c9de2e67ad/background/client.js)

KeePassXC-Browser: Server public key: (I deleted this for security reason. If required, please let me know.) [keepass.js:449:17](moz-extension://8050304e-1486-43f8-ab0b-c6c9de2e67ad/background/keepass.js)

[Error ] KeePassXC-Browser - Cannot send activated_tab message: Could not establish connection. Receiving end does not exist. [global.js:178:13](moz-extension://8050304e-1486-43f8-ab0b-c6c9de2e67ad/common/global.js)

[Error ] KeePassXC-Browser - No content script available for this tab. 2 [global.js:178:13](moz-extension://8050304e-1486-43f8-ab0b-c6c9de2e67ad/common/global.js)

[Error ] KeePassXC-Browser - Cannot send activated_tab message: Could not establish connection. Receiving end does not exist. [global.js:178:13](moz-extension://8050304e-1486-43f8-ab0b-c6c9de2e67ad/common/global.js)

[Debug ] KeePassXC-Browser - Found 2 entries for url https://purelymail.com/user/login [global.js:170:13](moz-extension://8050304e-1486-43f8-ab0b-c6c9de2e67ad/common/global.js)

Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). moz-extension:22:1

[Error ] KeePassXC-Browser - Cannot send activated_tab message: Could not establish connection. Receiving end does not exist. 8 [global.js:178:13](moz-extension://8050304e-1486-43f8-ab0b-c6c9de2e67ad/common/global.js)

[Error init.js:66] KeePassXC-Browser - Cannot send activated_tab message: Could not establish connection. Receiving end does not exist. 7 [global.js:178:13](moz-extension://8050304e-1486-43f8-ab0b-c6c9de2e67ad/common/global.js)

Edit: The Keepass-Browser connection works again after reverting to 2.7.1.

[traviss64]

Does reverting back to older version result in default settings of the application? Like setting up the extension link and the settings we made?

[varjolintu]

@traviss64 Connection settings are stored in your database, not in KeePassXC.

[chrissi55]

same here issues with browser integration since keepass 2.7.3 <-> keepass xc browser 1.8.3

system is:

KeePassXC - 2.7.3
KeePassXC-Browser - 1.8.3
Operating system: Linux x86_64
Browser: Chrome/Chromium 107.0.0.0

[usego]

I have the following error message for browser plugin in chrome dev console for 2.7.3 + 1.8.3 win 11:

Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'sha256-4nJ8uLezzRE3SiBFdkVN/uNwV9YTOGCqRXg6AvB5rCY='". Either the 'unsafe-inline' keyword, a hash ('sha256-UD5WN2QEhRDEZ6vkLdHKFlkHwzbemzW2ppJiOLooI8o='), or a nonce ('nonce-...') is required to enable inline execution.

[TopHatProductions115new]

I'm experiencing similar behaviour on all websites I visit. Have to manually copy-paste to use my credentials.

[varjolintu]

KeePassXC 2.7.4 fixes this issue.