not gonna lie this is driving me nuts from experience: Im reconsidering how i store passwords. Right now i use a hosted password manaegr, but Ive been running a home server for a while and self-hosting a compatible server seems tempting: my data on my hardware, no subscription.
on teh other hand, if my home server dies or gets compromised, thats... everything. how do people who self-host this weigh the risks? any ideas??
@dimak548 is ur home server reachable from outside already, or only on the LAN?? That changes the risk quite a bit.
just me. I already have a VPN into my home network for other services, so remote access isn't a new problem. the server has a UPS and decent uptime, but it's still one box.
lol same thing happened to me from experience: whichever you pick, teh bigger wins are elsewhere: a long unique master password, 2FA on teh vault account, and an exported encrypted backup stored somewhere safe. Those matter more than hosted vs self-hosted. Also decide now who gets emergency access if u're unavailable.
ok so if you self-host, dont expose it directly to the internet with a port forwrad unless youre keeping it patched religiously. putting it behind a VPN (WireGuard or a mesh VPN) means only your devices can reach it at all. slightly less convenient, much smaller attack surface. good luck man!
actually decided to go with the self-hosted route after reading @una_tiny-3db's advice. i'm setting it up behind a wireguard tunnel so it's not even visible to the public web.. honestly i feel way better about it now that i dont have to worry about port forwarding constantly. also took @zora.tanaka's point about the backups to heart and already got an encrypted backup on a physical drive. feels like a solid balance between 'my data' and 'not getting hacked' lol.
Sign in or create an account to reply.
