I am hosting on Home Assistant which itself gets a backup to my Google drive and my personal machine. So there are two backups, as long as HA doesn’t create a corrupted backup 3 weeks in a row I am good.
I would rather lose my passwords than have my password database be accessed by someone else. Most websites have a “forgot password” function, and for passwords that don’t have that (e.g. to decrypt my hard drive or log into my computer) I’ve memorised the passphrase and always type it manually anyway. And for passwords where neither applies, it’s probably not a huge loss anyway if I’ve not prepared for the possibility of losing my password db for that particular password.
All your services should be using https. Vaultwarden in particular won’t even run without https unless you bypass a bunch of security measures.
This is how to setup local only and external https, I highly recommend this as a baseline setup for every homelab. It allows you to choose how much security you want on a per app basis and makes adding new apps trivially easy.
Vaultwarden ftw
Exactly! Self hosted FTW. Chances of a data breach… Typically pretty minor if you are smart.
Chances of losing the data is higher with selfhosting too. Unless you’re doing some sort of multizone replication, or course.
I use syncthing so there’s a copy of my password database on each of my devices.
Yeah. Daily and weekly cloud backups solve that for myself for sure.
I am hosting on Home Assistant which itself gets a backup to my Google drive and my personal machine. So there are two backups, as long as HA doesn’t create a corrupted backup 3 weeks in a row I am good.
Borg backup to borgbase is not very expensive and borg will encrypt the data plus the vault is also encrypted
I would rather lose my passwords than have my password database be accessed by someone else. Most websites have a “forgot password” function, and for passwords that don’t have that (e.g. to decrypt my hard drive or log into my computer) I’ve memorised the passphrase and always type it manually anyway. And for passwords where neither applies, it’s probably not a huge loss anyway if I’ve not prepared for the possibility of losing my password db for that particular password.
As long as you’re still signed into BW from any of your devices, you can always export the vault from there.
(But yes, actual backups are always a plus)
Keep vaultwarden behind wireguard for local only access then also use https certs and good master password. Very secure like this
Why https if the traffic is already encrypted by the vpn?
Security in layers.
All your services should be using https. Vaultwarden in particular won’t even run without https unless you bypass a bunch of security measures.
This is how to setup local only and external https, I highly recommend this as a baseline setup for every homelab. It allows you to choose how much security you want on a per app basis and makes adding new apps trivially easy.
https://youtu.be/liV3c9m_OX8?si=TSWXoN_8SJDpAHaW
+1 for a self-hosted Vaultwarden instance. If you’re technically capable and have extra hardware laying around this is the best way to go.
Although a backup is still required or you are gambling on hardware outliving your need for your data.
Anyone with the knowledge to self host will quickly discover 3-2-1. If they choose to follow it, that’s on them but data loss won’t be from ignorance
100%. Make sure to follow the 3-2-1 backup rule with all things you do.