Currently I manage my passwords in an archaic but secure way, which is simply to synchronize a directory where I have my Keepass database between my devices, and I say archaic but secure because even if my Nextcloud server hosted on a VPS explode (where I have the database stored) I still have the databases stored locally, so I don’t lose anything.

I am currently interested in self hosting Vaultwarden although my biggest drawback is the fact that if my VPS were to fail for example I would not be able to access my database and if I lose access to the database I lose access to all my passwords. a pretty bad scenario.

So I have a question, what can I do to prevent that from happening? Apart from hosting everything on my own hardware of course, for now I prefer to use VPS for different reasons.

  • thelittleblackbird@lemmy.worldEnglish
    7·
    1 year ago

    May I ask what is wrong with your archaic setup?

    I have exactly the same config and I find it easy and reliable for not asking for a change.

    Am I missing some points or what is going on?

    • Xirup@lemmy.dbzer0.comOPEnglish
      1·
      1 year ago

      I didn’t mean to make it sound bad, although now that I read it again it sounds bad.

      With “archaic” I wanted to refer to the fact that it is not necessarily the most efficient in my opinion, because for example in the case of Nextcloud, to synchronize my Keepass directory with a directory on my phone I need an external app called FolderSync and there is no “Synchronize when detecting changes” option, every time I make a change I must manually synchronize or wait for a scheduled synchronization to take place, and it is not exactly the most efficient, unlike with Bitwarden/Vaultwarden because synchronization is immediate.

      And I know that in KeepassDX for example I can directly access my database and load it from there, but every time I make a single change when entering Keepass it says that “I lost connection to the file” (Something like that) and I have to go manually and choose the file again, I would prefer to have my passwords always in sync.

      • thelittleblackbird@lemmy.worldEnglish
        1·
        1 year ago

        OK got what you mean.

        For avoiding the cases you are describing I use several plugins for the keepass (original flavour) so in my desktop it syncs directly with the cloud.

        And in my android I use keepass2androd thst is able to open the database from the cloud too.

        Regards

    • vegetaaaaaaa@lemmy.worldEnglish
      1·
      1 year ago

      I have the exact same setup and it’s woking fine, nothing wrong with it.

      My only gripe with KeepassXC is that you can’t share - or so I thought - a subset of passwords from your keepass database with other people, without sharing the full database and master password. But I just read that it is in fact possible

  • 7Sea_Sailor@lemmy.dbzer0.comEnglish
    3·
    1 year ago

    Part of the fun of selfhosting is the challenge of figuring these things out and building your solutions. If you decide to go with the selfhosted bitwarden variant, there are a couple of options:

    1. you can directly dump the entire database on a fixed schedule, compress it into a gzip archive, and store it in a separate location on your VPS. These backups take up very little space and can, with the help of a script, be automated very well.
    2. you can use one of the plenty existing bitwarden backup containers that are made for this exact purpose and might offer a more comfortable setup.
    3. with any of these solutions, you’d probably want to pull these backups from your local storage to some remote storage, to ensure that in case of an accidental and complete server wipe, no data is lost / a recent backup is available. this can be done with solutions like rclone, to copy the files from your server to a remote location, like an FTP server you’ve rented or any cloudstorage you may have available.

    There’s probably even more options, but these are the ones I could think of quickly. If you have questions or need help regarding any of these, let me know, and I’ll send you additional ressources to read through.

  • PriorProject@lemmy.worldEnglish
    1·
    1 year ago

    So I have a question, what can I do to prevent that from happening? Apart from hosting everything on my own hardware of course, for now I prefer to use VPS for different reasons.

    Others have mentioned that client-caching can act as a read-only stopgap while you restore Vaultwarden.

    But otherwise the solution is backup/restore. If you run Vaultwarden in docker or podman container using volumes to hold state… then you know that as long as you can restart Vaultwarden without losing data that you also know exactly what data needs to be backed up and what needs to be done to restore it. Set up a nightly cron job somewhere (your laptop is fine enough if you don’t have somewhere better) to shut down Vaultwarden, rsync it’s volume dirs, and start it up again. If you VPS explodes, copy these directories to a new VPS at the same DNS name and restart Vaultwarden using the same podman or docker-compose setup.

    All that said, keeypass+filesync is a great solution as well. The reason I moved to Vaultwarden was so I could share passwords with others in a controlled way. For single-user, I prefer how keypass folders work and keepass generally has better organization features… I’d still be using it for only myself.