Vaultwarden handles the syncing for me.
However I do export backups on both my phone and laptop just in case.
Vaultwarden handles the syncing for me.
However I do export backups on both my phone and laptop just in case.
It's true re adding passwords while the server is offline, but my server runs 24x7 and it's never down for more than a few minutes. If it goes down, I fix it. I also backup the encrypted DB regularly to cloud, so there is little risk of data loss. I am a very satisfied Vaultwarden user. Especially because it allows password sharing with my family. Everyone has an account.
I use KeepassDX syncing via Nextcloud, works flawlessly. I also used to use Keepass2Android, also works very well.
Can you elaborate on the "nextcloud doesn't support 2-way syncing on android" statement? I can sync my Keepass database back and forth without issues.
I am also using KeepassDX and Nextcloud. I've had this setup for years and never had an issue with syncing.
I see where you're coming from. I also really wanted that in my early days of android and nextcloud. Turns out, nowadays you don't really need that for most use cases, and definitely not for KeePass syncing. Nextcloud app for android exposes all the files via content framework and KeePassDX can sync two ways via that. Other apps like Keepass2Android even have direct nextcloud support via WebDAV, though these days I prefer KeePassDX a little bit more for unrelated reasons.
I recommend you try either KeePassDX or Keepass2Android and see for yourself.
Also, most file managers support CF and will show you your nextcloud files as if they were real files on the device, even without "real" two way sync, and most other apps will be able to save & open files directly from nextcloud.
CF = content framework, android somehow decided that users shall not see and interact with "real" files and instead, have apps like nextcloud act like content providers and expose a file-like API ...whatever, it is what it is, but in the end it works.
I'm currently using Material Files, but even android's default file manager, bundled with the OS, shows Nextcloud in the left sidebar (your mileage may vary on this one, as each phone vendor tend to customize it a bit).
As for my setup, there's really not much to it: I selfhost nextcloud, have KeePassDX and the Nextcloud app, and when you setup KeePassDX, select "Open existing vault" and in the sidebar you should be able to select Nextcloud and pick files from there.
Note: For Material files, and most file managers really, nextcloud might not show up by default ("security" or something), but you can "add external storage" and give it permissions.
I've run into this issue with obsidian, but for whatever reason I haven't had any issues with keepassdx.
When opening an existing keepass vault, on the left there's an "Open From" pullout menu. You should be able to select your nextcloud from there. Then find your keepass file and it'll just work.
I don't know why, but obsidian doesn't have the same file picker. There's no "open from" menu. So you just have to drill into the filesystem, find the folder nextcloud is using, and choose your notes vault you've sync'ed in there. And for whatever reason, that seems to be the method that breaks Two-Way Sync.
On Android I use KeePassDx Syncthing-Fork. The handover was rough but the maintainer of the Play version joined researchxxl's team. Many on the Syncthing forum seem to have accepted research which is good enough for me. Also, KeePass's database in encrypted so no danger there.
Do you store TOTP in a seperate KeePass?
For me swappog between two Keepass DBs is annoying. I can't find anything that will sync my 2FAs.
I don't. Kinda seems silly to me.
To access a keepass file you already need 2 factors: the master password and access to the file.
Its not really 2 factors if it's stored in the same DB though.
I came from Bitwarden where the community recommendation was to not store passwords and 2FA together in the cloud. If a beach orccurs and you lose both then there wasn't a point in having the 2FA.
Less of a risk with a local solution but still not sure.
Yes, it is two factor, it's just that there is no additional factors required to get the TOTP.
If you don't use a password manager then you just remember your passwords. In this case the second factor is having access to a device that has your TOTP generator.
If you use keepass then you remember the password for your password db, and to access your passwords or TOTP you need access to a device with your keepass db.
If u have 2fa in the same database u can login on devices you don't trust. E.g. a coworkers computer/public computer in library.
Yeah. So that seems to remove the 2 from 2FA...
I keep everything in the KeePass DB. I wouldn't do this with a password manager that stores info in the cloud.
bitwarden
seems odd you say how cumbersome it is to manage and backup (not an issue I've faced though) and yet you are using some cumbersome alternative ?
Vaultwarden, no question. When I used KeePass, I had Synology Drive which worked well to sync.
Bitwarden.
Paid. Not because I need the added paid features, but because I value it and want to show my appreciation for the developers.
If you're using a keepass database, Keepass2Android can natively sync with many cloud options including self hosted and generic ones, even without specific "companion" apps. That's what I use. In my case, it's backed by my NextCloud, but it used to be Google drive before.
Just also sync the file on your PC, merging changes from different clients is part of the keepass database format and "just works".
Also VaultWarden works great if your can self host it, but I prefer keepass for a variety of features and integrations.
KeePass2Android is a fantastic project. I've been using it for 10+ years on my Android devices. Every once in a while I'll try a different variant, like KeePassDX, but I always return to the spartan look of KP2A. It "just works", with no extra fluff.
merging changes from different clients is part of the keepass database format and “just works”.
This is the best thing about KeePass in general.
I just switched back to vaultwarden. My vaultwarden data is backed up as part of my nightly backups. Desktop and android use bitwarden clients. Seeing as https://codeberg.org/small-hack/open-slopware/src/branch/main states keepassxc is using AI to create PRs. Otherwise you could see how seafile might work for you to sync your keepass db. If you are on android with termux you can run syncthing in termux which also works and avoids the issue with the syncthing fork
Paid bitwarden.
I use Bitwarden too. I now use the paid version (which is incredibly cheap) but I was able to sync between Android and PC without the paid for version iirc
The only (known to me) perk of the paid version is the encrypted storage (and probably the org feature).
So yeah. I see it more of a donation/appreciation than a service fee.
But the recent peice increase stung a bit.
Syncthing-Fork is still untrustworthy since the disastrous handover
Maybe I'm OOTL on this?
I thought everyone concluded that it was poorly communicated but ultimately no indication of any foul play.
I use keepass2android and "sync" via its native WebDAV support with my nextcloud instance as the source. Been working great forever.
I use Nextcloud + KeepassDX on android and KeepassXC on PC. Have never had an issue. Changes on desktop/phone are propagated virtually immediately across devices.
Vaultwarden with the Bitwarden Android app and browser extension for my desktop. I already have a solid system for backing up the important data for all my docker containers. As soon as I added it, it was automatically added to that process.
My spouse has an account so if I die she can gain access to my passwords with a simple request. That's function is important to me.
Personally, I use Keepass with syncthing and it works fine enough. If you don't really trust the new person behind Syncthing-Fork, you could always install the older version before the handover (I think before v3.4?).
If you really don't trust syncthing at all, you could just manually back it up. New passwords aren't made every day, so you could just copy the passwords database over between your devices whenever there's a change. That's what I did before I heard about syncthing, and is what I do with my music still, since I don't regularly update what music I listen to.
KeepassXC and Nextcloud. Been working fine for years.
Same setup here. Worked for years and I've no plans to switch. As long as Nextcloud is up, bidirectional editing is simple. Trouble comes when one of the clients edited the KeePass file and can't sync.
Keypass with the vault loaded onto a free OneDrive account.
Just back it up occasionally.
Nextcloud and favorite the file. It's worked reliably forms for years. I don't need to create new passwords on my phone, though.
Keepass for Android, my database is stored on OneDrive. Easy access on my win pc and android (KPA has built in sync for many cloud storage providers)
What's the problem with Nextcloud? I use KeepassDX (on android, KeepassXC on desktop) with the database on Nextcloud and don't have any problem syncing.
I use proton and it seems to work just fine for me
I use passwordstore.org which is basically a bash script that wraps GPG; but there is an Android client as well.
Everything is stored in encrypted files tracked by git. Files are synchronized by git/SSH to a server I run.
That entry names are stored in plain text doesn't bother me; if somebody has broken into my system so well that they've copied my password store then the last of my concerns will be if they can easily find out if I have a password stored for example.org or example.net. At that point it doesn't matter if they can tell that I have a Jellyfin password stored, because that service is running on my server with clients installed on my phone & tablet.
And I handle key storage with a pair of Yubikeys which hold a copy of my private key. It can't be extracted (only overwritten). There is a physical copy kept on offline, disconnected storage, which could be an attack vector -- but if we're at the point of somebody breaking into my house to target my password management then all bets are off: you don't need to break my kneecaps with a hammer for me to tell you everything, I prefer to keep my knees undamaged.
For attachments I just add another entry; /services/example.org-otherThing - there's nothing stopping you from encrypting binary data like an image.
And when it comes to convenience: I have a set of bash scripts that use Wofi to popup a list of options and automatically fill in data. Open example.org click the login field, hit meta-l, type example.org, hit enter and wait a moment: it'll copy and paste the username, hit tab for me, then copy/paste the password, then copy a bunch of random data into the clipboard buffer like 10 times before copying an empty string another hundred times to flush said buffer. meta-f for username only, meta-g for password only; it's honestly way more convenient for me than the 1Password setup I use at work.
I understand the point the video is making, but I think it's irrelevant if you keep the private key on something like a Yubikey.
Are there mechanisms for fully automatic synchronization on every file change and every initialization in the Android and console apps for password-store out of the box these days? Using Syncthing with password-store at the moment to get a user experience as close to that as possible. Had to switch from the Android app to Termux and the CLI because the app no longer supports usage with Syncthing.
There has to be, the PasswordStore app for Android can keep the GPG files in a storage location where other apps can read & write them. All you need is something to handle the synchronization.
I'm a control freak and prefer to do things like that manually, so I just use the built-in git & SSH based method it provides.
I'm running the standard version of syncthing through termux at the moment. It lacks some of the power management options, but otherwise I've experienced no issues.
I've been using KeePass for almost 20 years now, used to host the database on Google Drive. I started using Syncthing about a year or so ago, including Syncthing-Fork on my Android devices. It's nearly flawless - I sync the database across 6 devices (two phones, two laptops, gaming PC, NAS [which is backed up regularly]), so there is the occasional conflict maybe once every few months, but I think that's more user error than anything else. It's fairly easy to resolve since Syncthing clearly labels the affected file.
It's very important to remember that "Syncthing-Fork" IS NOT the official Syncthing project. Syncthing-Fork uses Syncthing under the hood while providing a mobile-friendly wrapper.
Edit - Re: Syncthing Fork "drama":
Catfriend1 (the original maintainer of Syncthing-fork) recently put in their 2 cents.
TL;DR - The new dev is fine.
For me personally, the fact that 1) devs from both F-Droid and Syncthing itself have reviewed and confirmed that the code is safe, and 2) the original maintainer vouched for the new guy, is good enough for me. There will always be those who refuse to trust anything, even from the original developer, and they are often the most vocal about it - i.e. the "vocal minority". Whether or not you want to listen to their criticisms is up to you. IMO, they're just beating a dead horse.
I still think a syncthing client of some form is ideal. As someone else mentioned there is the option of using the Syncthing Tray devs experimental android build. To avoid issues with sync-conflicts / maintain high-availability access to the most recent file, I sync the databse to a raspberry pi with the encryption option selected (not that the pi is untrusted per se, but it is a device that doesn't need access to the file, it just serves the most recent changes to other devices since often my laptop / phone / desktop are not all on at the same time).
OpenCloud seems promising. It's a fork of ownCloud from former developers of ownCloud, lighter weight than NextCloud, it uses flat files to store data rather than a DB, and it has an Android client on F-Droid (and Google Play).
I'm hesitant about OpenCloud. Their parent company is Heinlein Group, whom I know nothing about, nor can I find anything about their reputation. The website uses a lot of marketing fluff, which puts me off already.
If you're curious, their GitHib issues and website have a bit more about them: https://github.com/opencloud-eu/opencloud/issues/231
The Heinlein Group, to which OpenCloud belongs, is probably best known as the operator of the email provider mailbox.org, but also develops OpenTalk, an open source video conferencing solution.
from heise.de.
Being the owner of mailbox.org doesn't mean anything to me, but it's context. And there's more info in that GitHub issue's links.
My impression is that they know what they're doing when it comes to production ready software--I share the OPs concerns about the syncthing-fork maintainer--and they have the funding and acumen to stay in business, meaning their software will be maintained.
I can't endorse them beyond my own personal opinion though. I don't have any info beyond what a few hours of digging turned up last time I looked into them.
This bit from the heise.de article stood out:
Kiteworks, on the other hand, is less than enthusiastic about – a closed group of developers who are now using the same code in their own company that they already developed under Kiteworks or ownCloud? For Kiteworks, this smells like poaching, so the company is going on the offensive: in an interview with heise online, Kiteworks CEO Jonathan Yaron stated that he intends to sue Peer Heinlein under German and US law: "We love open source, but we won't let anyone steal from us".
facepalm
I'm a vaultwarden user, who likes the idea of both the bitwarden and the keepass way. Just to consider new possibilities, isnt it possible to put the keepass db in a private git (selfhosted forgejo or gitea). And sync the repo with an app like puppygit which syncs automatically everytime I open or close keepass. Is this a safe walkthrough?
Its a port of linux pass with git built in.
You backup your passwords in a private repo and sync back and forth. It's great if you already use pass
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| CF | CloudFlare |
| Git | Popular version control system, primarily for code |
| NAS | Network-Attached Storage |
| SSH | Secure Shell for remote terminal access |
| VPS | Virtual Private Server (opposed to shared hosting) |
5 acronyms in this thread; the most compressed thread commented on today has 14 acronyms.
[Thread #167 for this comm, first seen 15th Mar 2026, 17:10] [FAQ] [Full list] [Contact] [Source code]
all 85 comments