Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot connect KeePassXC-browser #6042

Closed
Stephan-P opened this issue Feb 1, 2021 · 24 comments · Fixed by #6050
Closed

Cannot connect KeePassXC-browser #6042

Stephan-P opened this issue Feb 1, 2021 · 24 comments · Fixed by #6050
Labels

Comments

@Stephan-P
Copy link

Stephan-P commented Feb 1, 2021

Upon return from 5 weeks offline and upgrading KPXC to v2.6.4 I find that browser integration with both Vivaldi and Edge browsers is failing.

I've tried without success:

  • Disable/enable browser integration in KPXC and restart KPXC
  • Remove connected databases from KPXC-Browser and try to connect to KPXC
  • Remove/reinstall KPXC-Browser extension from both browsers

In any case, the function "Connect" in KPXC-Browser does not cause any effect. It simply doesn't do a thing.

Is there a way to reset the browser integration and remove any possible remaining pieces of data that may now include stray pointers?

=================

KeePassXC - unknown
KeePassXC-Browser - 1.7.5
Operating system: Win64
Browser: Chrome/Chromium 88.0.4324.99

=================

KeePassXC - Versie 2.6.4
Revisie: 34a78f0

Qt 5.15.2
De foutopsporingsmodus is uitgeschakeld.

Besturingssysteem: Windows 10 Version 2009
CPU-architectuur: x86_64
Kernelversie: winnt 10.0.19042

Geactiveerde extensies:

  • Auto-type
  • Browserintegratie
  • SSH-agent
  • KeeShare (getekend en ongetekend delen)
  • YubiKey

Cryptografische bibliotheken:

  • libgcrypt 1.9.1-unknown
@Stephan-P Stephan-P added the bug label Feb 1, 2021
@droidmonkey
Copy link
Member

Go to database settings in keepassxc (Database-> Settings) and click the browser integration category. Then clear out the encryption keys in there. You can also go to application settings and make sure the browsers are setup properly.

@user858753257
Copy link

Have the same issue with the new Mac M1 version 2.6.4

I'm using MS Edge and can't connect to the database .

I have tried the hint above but no success .

Every time I click "connect" the browser extension says "key Exchange was not successful "

@floeschie
Copy link

floeschie commented Feb 1, 2021

Have the same issue with the new Mac M1 version 2.6.4

I'm using MS Edge and can't connect to the database .

I have tried the hint above but no success .

Every time I click "connect" the browser extension says "key Exchange was not successful "

Same here, since I upgradet KeePassXC to version 2.6.4 via HomeBrew this morning. As soon as the upgrade was done, my browsers (Chrome, Firefox) were not able to connect to the database anymore.

  • MacOS Big Sur
  • Firefox 85.0
  • Chrome Version 88.0.4324.96 (Official Build) (arm64)
  • KeePassXC Chrome Browser Plugin 1.7.5

@droidmonkey
Copy link
Member

droidmonkey commented Feb 1, 2021

For macOS you probably need to restart your browser or computer. New software causes all sorts of problems for macOS. Their software security settings often cause random things to fail on upgrade without restarting.

@floeschie
Copy link

For macOS you probably need to restart your browser or computer. New software causes all sorts of problems for macOS. Their software security settings often cause random things to fail on upgrade without restarting.

Already did that... 🤷

@Stephan-P
Copy link
Author

Go to database settings in keepassxc (Database-> Settings) and click the browser integration category. Then clear out the encryption keys in there.

That did the trick. Not immediately, though. I had to click the button "Connect" a couple of times before the connection was actually re-established.

@floeschie
Copy link

For macOS you probably need to restart your browser or computer. New software causes all sorts of problems for macOS. Their software security settings often cause random things to fail on upgrade without restarting.

Not sure if this is related: When I try to run keepassxc-cli and keepassxc-proxy from the command line (Terminal), I get this error:

% cd /Applications/KeePassXC.app/Contents/MacOS

% ./keepassxc-cli 
dyld: Library not loaded: /opt/homebrew/opt/libgpg-error/lib/libgpg-error.0.dylib
  Referenced from: /Applications/KeePassXC.app/Contents/MacOS/./keepassxc-cli
  Reason: image not found
zsh: abort      ./keepassxc-cli

% ./keepassxc-proxy
dyld: Library not loaded: /opt/homebrew/opt/qt/lib/QtNetwork.framework/Versions/5/QtNetwork
  Referenced from: /Applications/KeePassXC.app/Contents/MacOS/./keepassxc-proxy
  Reason: image not found
zsh: abort      ./keepassxc-proxy

So I thought it might be an issue with the HomeBrew cask and removed it. Then I downloaded the latest stable DMG file for Apple Silicon from the website, but could not install because I got an error message "KeePassXC os damaged and cannot be opened".

So I assume something is broken within the MacOS build?

@droidmonkey
Copy link
Member

droidmonkey commented Feb 1, 2021

Yah that's absolutely related. It shouldn't be pulling the libraries from your homebrew install, we deploy with those libraries in the dmg. @phoerious, I think the library names changed and we need to update the cmakefiles.

@phoerious
Copy link
Member

Gosh, yet another reason why Homebrew moving everything from /usr/local to /opt/homebrew was a TERRIBLE idea.

@floeschie
Copy link

floeschie commented Feb 1, 2021

Gosh, yet another reason why Homebrew moving everything from /usr/local to /opt/homebrew was a TERRIBLE idea.

I have no problem installing KeePassXC without HomeBrew, even though I prefer to install software this way. However, the DMG file seems to be broken as well:

Bildschirmfoto 2021-02-01 um 15 59 10

SHA256 checksums match.

phoerious added a commit that referenced this issue Feb 1, 2021
Since Homebrew moved all its stuff to /opt/homebrew, our hard-coded
install_name_tool patch magic stopped working. This patch uses
macdeployqt for all executables to prevent this kind of behaviour.

Fixes #6042
phoerious added a commit that referenced this issue Feb 1, 2021
Since Homebrew moved all its stuff to /opt/homebrew, our hard-coded
install_name_tool patch magic stopped working. This patch uses
macdeployqt for all executables to prevent this kind of behaviour.

Fixes #6042
@phoerious
Copy link
Member

Please try redownloading the build from the website and see if it works for you: https://keepassxc.org/download/#mac

@duminduweera
Copy link

I've installed the v2.6.4-2 and this seems to fix the issue.

@phoerious phoerious pinned this issue Feb 1, 2021
@user858753257
Copy link

Gosh, yet another reason why Homebrew moving everything from /usr/local to /opt/homebrew was a TERRIBLE idea.

I have no problem installing KeePassXC without HomeBrew, even though I prefer to install software this way. However, the DMG file seems to be broken as well:

Bildschirmfoto 2021-02-01 um 15 59 10

SHA256 checksums match.

Workaround : mount the installer -> copy the program to desktop. -> copy it in program folder .
I see this “bug” also in the last version

@user858753257
Copy link

I've installed the v2.6.4-2 and this seems to fix the issue.

Also the connection issue ?

@floeschie
Copy link

The issue is not fixed. Neither can I install the DMG file (v2.6.4-2) nor can I connect the browser plugin. Should I open a new issue?

@user858753257
Copy link

The issue is not fixed. Neither can I install the DMG file (v2.6.4-2) nor can I connect the browser plugin. Should I open a new issue?

Have you tried out my workaround ?

@floeschie
Copy link

No not yet. I wouldn't consider a workaround as a generic solution for this issue...

@phoerious
Copy link
Member

We seem to be mixing things up here. 2.6.4-2 is for ARM Macs and fixed the rpath issue with the CLI and browser integration. For everything else, we need more information.

@floeschie
Copy link

We seem to be mixing things up here. 2.6.4-2 is for ARM Macs and fixed the rpath issue with the CLI and browser integration. For everything else, we need more information.

I'm using a MacBookPro M1. Currently I don't have KeePassXC installed. So basically it's a fresh start.

Either way, I have no idea how to get KeePassXC Browser Integration running on my M1 Mac.

@phoerious
Copy link
Member

Try a reboot and if it persists, try clearing extended file attributes from either the DMG or the installed application:

xattr -cr /Applications/KeePassXC.app

@floeschie
Copy link

Try a reboot and if it persists, try clearing extended file attributes from either the DMG or the installed application:

xattr -cr /Applications/KeePassXC.app

OK, so here is what I did:

  1. Removed any KeePassXC app from the system
  2. Reboot
  3. Download KeePassXC DMG v2.6.4-2 from the website
  4. Mount the DMG (double click) - no drag'n'drop!
  5. Open Terminal
  6. Run the command @phoerious proposed in Cannot connect KeePassXC-browser #6042 (comment): xattr -cr /Volumes/KeePassXC/KeePassXC.app
  7. Head back to the Finder window that opens after double clicking on the DMG
  8. Drag & drop KeePassXC on the Applications folder icon

Result: KeePass is installed and browser integration works again 👍

Wondering what the xattr command changed? Was there something wrong on my machine specifically?

@phoerious
Copy link
Member

Probably. It's normal for macOS or Chrome to add the com.apple.quarantine attribute, but that should only ask for confirmation before running an application.

@Saj5h7
Copy link

Saj5h7 commented Feb 2, 2021

@phoerious @floeschie Solution worked, thank you.

@user858753257
Copy link

Installed the new version (-2) in my MBA M1 and now the browser works again . Thanks

droidmonkey pushed a commit that referenced this issue Feb 5, 2021
Since Homebrew moved all its stuff to /opt/homebrew, our hard-coded
install_name_tool patch magic stopped working. This patch uses
macdeployqt for all executables to prevent this kind of behaviour.

Fixes #6042
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants