192
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 May 2026
192 points (99.5% liked)
Selfhosted
59509 readers
139 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
Jesus, I'm tired of switching password managers.
KeePassXC + KeePassDX is probably the best option, with the downside of no way to sync easily (syncthing is probably the best option there)
I might switch back at some point, been getting frustrated with the bitwarden extension performance always being so poor.
My first password manager was KeePassXC.
Hooked it up with Syncthing, and I've never had issues aside from the occasion database duplicate.
Merge conflicts are a concern for KeePass, especially for those that don’t want to resolve them. Sync is difficult. AFAIK this is a very common issue with Syncthing setups.
Also, the portability from Bitwarden to KP leaves a bit to be desired, though that’s probably 90% on BW.
I'm using Keepass2Android (and KeepassXC). It can copy the database from/to an sftp server, so it can easily merge the entries. I don't have the sftp server exposed to the Internet, because when I'm not home, nobody will change the database at home.
I've been using KeePass with Syncthing for 5+ years now and I think I've only had a sync issue once in all this time.
Granted I do make sure I only use the database on one device at a time (so not making edits on desktop and my phone at the same time) and I'm using XC and DX clients not the OG KeePass program.
I'm curious what is causing sync issues to make it "common", I use my db every day.
Yeah, it’s not an uncommon use case to accidentally or even intentionally edit the database on two online devices - I do it all the time when I want a new login to be used on my laptop right after I signed up for some new website on my PC, and the laptop just happens to have an “unpushed” change from last evening, or I edit the new login’s metadata, or whatever.
With this, I’d have to keep a mental model of the versioning of each database and avoid even touching my phone like the plague if KeePass is open on my computer.
It’s not that big of a deal, it’ll probably be a problem once every few months, but it’s annoying to keep track of and worth talking about.
It's really not that much of an issue. I sync my database between several devices, some of which are only used occasionally. Rarely do I ever have a merge conflict.
If you're editing the database on multiple devices before they have a chance to sync with each other, maybe stop doing that. That's what causes merge issues.
Sync however you want. Syncthing, Nextcloud, Dropbox, Gdrive etc.
Syncthing is the way to leave Google Drive, etc.
I use Nextcloud myself, but if people don't want to host a server or fuck with syncthing, they can sync it however they want as long as they use a strong enough master password/phrase (which they should be anyway.).
Oh, well, I'm talking about not having to password-lock and unlock your stuff constantly. For long-term storage, sure, that's fine; anything else would be way too tedious, though, no? I guess it depends on your use case and if you could locally automate the locking and unlocking or something.
I'm not sure what you mean. On my computer, I have to unlock the database every so often (you can set how long) with my master password. On my phone I unlock it with my fingerprint. The method of syncing the database is irrelevant.
Oops, I thought you were talking about long-term storage of files in general, like videos and docs or something, not a password database! Never mind.
Is there a proper syncthing android client now, after the official android client was discontinued?
Yeah the performance is what made me install the desktop app, but then it's 1gb in size
I use KeePass with KeeAnywhere. KeePass can natively sync over network share, FTP, or WebDav. With plugins, it can sync over SSH, FTPS, Amazon S3 compatible buckets (including open source compatible versions you host yourself), Azure, Box, Dropbox, Google Drive, OneDrive, and more.
Rclone with any cloud provider is another great option that's seldom mentioned. I posted my setup as a comment on another post. You may find it here - https://programming.dev/comment/23849767
XC is really nice, but the devs are kinda dicks about not integrating some sort of syncing option, instead telling everyone who asks to "just point it to a local folder and use <insert sync tool of your choice> to keep that folder updated." Which isn't terrible advice, but some of us don't have that option on managed devices.
KeePass isn't going anywhere. They're also dragging their feet on passkey support, so you might go with KeepassXC.
@slate
Wasn't there some commotion a few weeks about KeepassXC and vibe coding?
@RonnyZittledong
Yeah, there was. It was forked because of that, actually: https://codeberg.org/ChiPass
Their AI policy looks very reasonable, and they certainly aren't vibe coding. Everything is rigorously reviewed and tested by a handful of experienced, competent humans.
They also don't effectively allow collaboration though, which is my cheif reason for using a cloud hosted password manager.
KeePass isn't meant to be used that way. It's a personal password manager. Always has been.
Valid. But it's also valid that it now doesn't work for me or anyone who also helps manage other people's lives or works on a team ¯_(ツ)_/¯
What is "collaboration" in this context?
Sharing passwords between groups of people so everyone always has the up to date version. Not breaking the world if two people try to modify the same entry as some file syncing solutions do.
Sure they do. Multiple people can have a file open at the same time. I use it for exactly this every day at work.
With KeePassXC, that is. I don't know if other flavors have different support. I use XC primarily for the browser extension.
And you can both modify the same things without causing horrible conflict issues? And you can share only parts of your vault with someone rather than having entirely different vaults you have to switch between? I'm assuming you mean putting the file somewhere like Google Drive, and you can access it offline even if you can't edit it offline? For feature parity with Bitwarden, obviously ideally one could edit any time and it would resolve problems when it came back online if there were any but Bitwarden doesn't allow this.
Yes, no conflicts. I don't know if you can only share part of vault; I just created a separate one for a separate team.
I wouldn't put it in Google Drive or anything like that. The separate sync logic will definitely cause conflicts.
I'm not worried about having access if I'm offline, because if I'm offline I'm not going to be able to log into anything anyway.
I guess a laptop, server, IoT device, or WiFi connection when your main device doesn't have internet is out of scope for you?
Like fixing my laptop and not wanting to type the new password into my phone instead of copy/paste, sync when online?
And how are you sharing a file, to multiple people anywhere in the world realtime ish, without a cloud service you or someone else hosts? Doesn't that necessitate some syncronization logic?
Password Store is the answer, if you don’t need passkey support. You can be sure it can’t be sold. It’s the golden middle: not self hosted, but not owned by anyone.
I just got Bit warden this year! Gah. Where are we jumping?
Full circle to sticky notes on monitor.
Took me like 5 minutes to move back to KeepassXC.
i want to switch back to KeepassXC, but I very heavily use aliases in Proton Pass and can't figure out a good way to still create those on the fly AND use Keepass as my default pass provider