-
-
Notifications
You must be signed in to change notification settings - Fork 195
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 to KeePassXC #2053
Comments
Did you check the AppArmor settings from the Troubleshooting Guide? |
I had the same problem today, and I've noticed that firefox has updates itself to version from |
To check this, go to |
FYI: possibly unrelated, but I experienced the same on a fresh install on 22.04 and none of the debugging tips produced anything that made sense to me. The proxy would start, but the connection would fail. What did eventually work was not using firefox deb but instead installing the snap version (pretty much the opposite of what's recommended in most issues) and then applying the flatpak permission tips from #1426. |
@jhard that means you did not perform the AppArmor troubleshooting action correctly with your deb install. |
I'm closing this as a duplicate. Please continue the discussion in the pinned issue: #1863. |
I am running the deb version of firefox 121 on a fresh install of Ubuntu 23.10; I installed the KeePassXC-browser extension, but it says
Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings.
When I clickReload
, it saysCannot complete key exchange
.keepassxc-proxy is not running, but trying to launch it manually does not change this behavior. The output of
sudo strace -f -p $(pgrep firefox) 2>&1 | grep keepass
isI have tried disabling integration, removing the extension, and rebooting.
The browser integration is running on an old laptop running the same versions of firefox, keepassxc, and keepassxc-browser but Ubuntu 22.04; interestingly, a few weeks ago I started having to click
reload
on the browser extension after every suspend/resume on that laptop.Debug info
The text was updated successfully, but these errors were encountered: