this post was submitted on 27 Jun 2026
49 points (100.0% liked)

Selfhosted

60177 readers
559 users here now

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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. 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.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
49
Vaultwarden while allowing family emergency access (piefed.blahaj.zone)
submitted 17 hours ago* (last edited 17 hours ago) by CorrectAlias@piefed.blahaj.zone to c/selfhosted@lemmy.world
21 comments fedilink hide all child comments
 

Hi everyone.

Given some recent.. issues with Bitwarden's leadership, I've been toying with Vaultwarden. It's been great, and supports pretty much everything I need.

I currently locally host the vault, but I'm realizing that this could cause problems for my family if something were to happen to me. While not technologically inept, if my server at home crashed they would have no idea how to access it, and they would lose all of the passwords.

I was thinking that a vps might be a better choice for this, possibly with some reboot automation in case of outages. That would allow them enough time to initiate the emergency access and import everything before anything happens to the passwords.

I've also got encrypted M-disc backups of the most important passwords with timestamps of when they were last set. I've demonstrated and written down instructions on how to decrypt these. Of course I also have other backups, but I doubt they'd be able to retrieve the non-physical copies of the backups.

Anyway, is that what most people here do with Vaultwarden, use a VPS with mTLS or VPN? To add, I would only use a tunnel for this if I go this route, so no open ports.

you are viewing a single comment's thread
view the rest of the comments
[–] thehatfox@lemmy.world 10 points 15 hours ago (2 children)

A VPS is going to have all the same problems as a local server in terms of inexperienced users, and will also add all the extra hassle of managing and paying for the VPS account.

I would say the best options for emergency access are local backups and documentation, which you already have. You could also consider keeping additional copies of essential passwords (like email accounts etc) in a simpler vault like Keepass. Or even physical copies written down in a security envelope in a safe.

[–] Creat@discuss.tchncs.de 1 points 11 hours ago

A VPS is like 5 bucks. Which isn't nothing but when used as a redundancy or place to send (reasonably sized) backups, it's cheaper than most alternatives. It's also still a form of "self hosting", at least for me.

Exporting, maybe on a schedule, to a keepass to keep somewhere, also works of course. But when hosting the only/main instance at home you'll have at least one single point of failure, most likely many. Internet connection, server, network/switches, ...

[–] s38b35M5@lemmy.world 1 points 11 hours ago

+1 for simple. Something you don't need to host.