159

For example, something that is too complex for your comfort level, a security concern, or maybe your hardware can’t keep up with the service’s needs?

you are viewing a single comment's thread
view the rest of the comments
[-] ChrislyBear@lemmy.world 8 points 1 year ago

Oh man, that's actually really good advice! I recently switched to Vaultwarden, but you're right: If my server goes down, I can't even restart it, because the password for my account is in there! Damn! Close call!

[-] Limit@lemm.ee 17 points 1 year ago

Well with bitwarden/vaultwarden you can have a copy of your entire vault on your phone or computer or both... so even if your server was totally dead, you'd have access to your passwords. Solid backups is a must, I follow the 3-2-1 rule on super critical systems (like vaultwarden) and test that you can actually recover. Something as simple as spinning up a VPS, testing a restore, testing access, see if that could work in a pinch until you get your server back online, then tear it down. Linode is very cheap for this kind of testing, it'd only cost you a few pennies to run a "dr" test of your critical systems. Of course you still want to secure it, I'd recommend wireguard or tailscale instead of opening access to your DR node to the internet, but as a temporary test it's probably fine if your running patched up to date versions of docker, vaultwarden, and I'd always recommend putting a reverse proxy in front like nginx.

[-] newIdentity@sh.itjust.works 11 points 1 year ago

Usually the password are also stored locally.

I can definitely access all my passwords offline with bitwarden

this post was submitted on 01 Aug 2023
159 points (97.0% liked)

Selfhosted

39253 readers
180 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS