Selfhosted
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.
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!
view the rest of the comments
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.
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'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.
Hmm, I'll have to play around with it a bit more then to see if I can trigger it.
My only gripe is the browser autofill. Sometimes it triggers correctly and sometimes it doesn't. I've noticed if I let KeePass add in a new login itself after I've manually entered it then it's much more receptive to suggesting that login correctly going forward. So I'm tempted to create a brand new database and login everything manually so KeePass will create the database entries itself to fix my gripe.
I switched over to keepass yesterday, and surprisingly the import from BW was perfect (as far as I can tell), even passkeys came over just fine.
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.
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.
I'm using KeeWeb on Mac and Windows and Keepass2Android on my Android device and I don't have any issues at all. I'm storing in OneDrive though, this is the one thing I'm using it for still.
My first password manager was KeePassXC.
Hooked it up with Syncthing, and I've never had issues aside from the occasion database duplicate.
Right, and it has a neat merge-database feature anyway, so no excuses for those holding back!
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
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.
That's a neat one, although it doesn't look like KeePass supports passkeys yet, at least I don't see it in the feature list.
Are you trying to use a passkey to unlock the database or for authenticating with other websites? KeePass can natively do TOTP. There's also plugins to do that. Including one that allows KeePass to be a native Windows 11 PassKey Provider.
For other websites, if I search for 'passkey' on the KeePass website feature list nothing comes up. Plugins in a password manager sketch me out a bit tbh lol
See here: https://keepass.info/help/base/placeholders.html#otp Also worth pointing out that most plugins are open source. You can read the source and compile them yourself, if you'd like.
This is for OTP not Passkeys it seems?
How do you go about loading plugins on the Android version for sync with your setup?
I don't usually use plugins on the Android version. I don't use the Android much, actually, just due to my use patterns. There's actually several different KeePass Android apps. KeePass is open source and the database format is documented. So anybody can make a program that uses the same database. The one I use is Keepass2Android, seems to be one of the popular ones. Looks like it also can natively generate TOTP. Apparently it has some sort of plugin system, but I've never needed to use it because it can pull my password database out of my Google Drive natively.
You need to specify what kind of passkey to be more specific. There's several different algorithms. HOTP and TOTP are very widely used. It's what Google Authenticator and the like use. If you have something very proprietary, like the old RSA keys, that probably can't be emulated by any software. Or they could, but you can't get the secret to be able to do that.
Yeah the performance is what made me install the desktop app, but then it's 1gb in size
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.
I ended up using Keepass2Android and just pointing it at my webdav server, it seems to work pretty well!
On desktop it's already taken care of since I put the DB in my folders that already sync via Syncthing.
I love K2A, been using it for well over a decade now. I really should toss the dev some cash... They've kept the UI consistent for years.