Sign in Subscribe

KeepassXC issues

KeepassXC issues

There have been recent issues reported with the KeePassXC browser extension connecting to Brave (and sometimes other Chromium-based browsers) as of late 2025 and into early 2026. Here are the main patterns from user reports and GitHub issues:A notable problem appeared in January 2026, where the KeePassXC-Browser extension suddenly stopped connecting to the desktop app across multiple browsers, including Brave, on macOS (e.g., MacBook Pro M3). Users saw no response when trying to connect, or the extension showed as active but couldn't reach KeePassXC. This affected Brave along with Edge and Chromium. (GitHub issue #2816 in keepassxreboot/keepassxc-browser). You may also encounter it on Linux.

Earlier in 2025 (around May), Brave users reported intermittent or partial failures: the connection worked after updates/downgrades/reconnects but often broke again after restarts, with errors like "Message encryption failed" or inability to reconnect properly. Some involved proxy/encryption handshakes failing.

The problem appears to center around GitHub issue #2816 in the keepassxreboot/keepassxc-browser repository (opened early January 2026), where the KeePassXC-Browser extension suddenly stopped connecting to the desktop app on macOS (specifically reported on MacBook Pro M3, but affecting Chromium-based browsers like Brave, Edge, and Chromium). Users described the extension showing as active but unresponsive—no connection dialog appears when clicking to connect/re-associate, and basic troubleshooting steps didn't resolve it immediately. T

his seems part of a broader wave of macOS-specific connection failures around late 2025 into early 2026, often tied to KeePassXC updates (e.g., versions around 2.7.x), code-signing changes in macOS packaging, or native messaging handshake problems. Related issues (#2823 for Firefox on macOS, #12713 in the main KeePassXC repo) mention similar symptoms: "Cannot connect to KeePassXC" → "Key exchange was not successful" after reload, or no response at all, sometimes after an app/OS update overwrote configs.Detailed Fix Steps (Focused on macOS + Brave)These steps combine official troubleshooting, user-reported resolutions from the issues, and common workarounds that fixed it for most people in similar reports:

  1. Verify Basics First (Quick Checks)
    • Ensure KeePassXC is the official .dmg version from https://keepassxc.org (not Homebrew, MacPorts, or outdated builds—some had code-signing issues post-update).
      Re-download the latest stable (as of Feb 2026, check for 2.7.11+ or newer patches; issue #12713 was fixed by re-downloading the signed .dmg).
    • Launch KeePassXC before Brave, unlock your database.
    • In KeePassXC: Go to Tools/Settings → Browser Integration → Ensure it's enabled, and check both "Brave" and "Google Chrome" (Brave often needs the Chrome box on macOS due to shared native messaging paths).
    • In Brave: Disable built-in password manager (brave://settings/passwords → turn off "Offer to save passwords" and "Auto Sign-in"). Also disable any other password extensions.
  2. Re-Pair / Re-Associate the Connection (Core Fix for Many)
    • In Brave, click the KeePassXC-Browser extension icon.
    • If it shows an error like "Cannot connect..." or nothing happens:
      • Click Reload (even if it fails with "Key exchange was not successful").
    • Open extension options (right-click icon → Options, or via brave://extensions/):
      • Go to Connected Databases tab.
      • Remove all existing database associations (delete entries).
    • Back in the popup: Click Connect / Reconnect.
      KeePassXC should now prompt to allow the new association—name it (e.g., "Brave on Mac") and approve.
    • Test by visiting a login page; the extension should detect and offer autofill.
  3. Clear Encryption Keys if Handshake Still Fails
    • In KeePassXC: Open your database → Database → Database Settings → Browser Integration tab.
    • Click Clear / remove any listed encryption keys or public keys for browsers.
    • Save, restart KeePassXC, then repeat step 2 to re-pair.
      This resets the secure channel and fixed "key exchange" errors in several reports.
  4. macOS-Specific Tweaks
    • Check for macOS security prompts: After re-downloading KeePassXC, right-click the app → Open (to bypass Gatekeeper if needed).
    • If you see code-signing errors (related to keepassxc-cli or browser native messaging): Re-download the signed .dmg as noted in issue #12713 fixes.
    • Temporarily disable macOS built-in password autofill: System Settings → Passwords → turn off AutoFill from iCloud/etc., to avoid conflicts (some users reported interference post-update).
    • Restart your Mac after changes (rarely needed, but cleared stale native messaging sockets for a few).
  5. If Still Broken
    • Update the extension: Check brave://extensions/ for KeePassXC-Browser updates (some late-2025 versions like 1.9.9.x had bugs; ensure latest).
    • Test in another browser (e.g., plain Chrome or Edge) to isolate if Brave-specific.
    • Review logs: In KeePassXC → Help → Show Application Log (look for native messaging errors). In Brave, enable developer mode on the extension and check console (right-click icon → Inspect popup).
    • If sandbox/permissions issue suspected: Avoid Flatpak/Snap installs on macOS (use official .dmg).
    • As a last resort: Uninstall/reinstall both KeePassXC and the extension, then re-pair from scratch.

Most users in #2816 and related threads (plus #2823) got it working again with steps 2–3 (removing old associations + re-connecting after clearing keys), especially after ensuring the latest signed macOS build. The issue was marked as needing more info initially but aligns with a post-update config breakage rather than a permanent bug.