this post was submitted on 12 Feb 2026
11 points (100.0% liked)

Flatpak

91 readers
11 users here now

founded 9 months ago
MODERATORS
 

Out of the box a browser installed via Flatpak can't communicate with KeePassXC using the browser extension because of Flatpaks encapsulation.

This can be fixed by adjusting the browsers Flatpak permissions, adding a wrapper for keepassxc-proxy to the browsers container and spawning keepassxc-proxy from within the container.

I built a script that does this for you. Currently supports Firefox, Librewolf and Ungoogled Chromium.

Have fun!

you are viewing a single comment's thread
view the rest of the comments
[–] refalo@programming.dev 1 points 4 hours ago* (last edited 4 hours ago)

I had a similar issue with firefox launched via firejail where I had to pass through the socket file it uses to communicate with.

If it helps anyone, this was my solution:

$ cat .config/firejail/firefox-common.local
include firefox-common-addons.profile
noblacklist ${RUNUSER}/app
mkdir       ${RUNUSER}/app/org.keepassxc.KeePassXC
whitelist   ${RUNUSER}/app/org.keepassxc.KeePassXC