Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


To host or to not host Bit/Vaultwarden? - Page 2
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

To host or to not host Bit/Vaultwarden?

2»

Comments

  • @matheny said:

    @BlaZe said:
    Don't self-host it. The last thing you'll ever need is, you're on a vacation, your tinder hookup ditched you, so now you trying to login into your pr0nhub account but the password is on your selfhosted vaultwarden. You realize that the host has planned for a maintenance for 30mins and thus your VPS would go down/inaccessible. You check after an hour and still your VPS is down. Host's status page say that one of their disgrunted employee fucked up the migration on purpose and now they are rebuilding the server from backups - which could take hours maybe? So now you are all alone in the hotel room, sipping wine in robe, thinking what if your tinder hookup hadn't ditched you at the last moment, how would things go by now.

    OR

    You'll now think about this day, when you created the thread, asking for opinions on selfhosting Vaultwarden and concluded to self host it.

    < /fun>

    If I'm going to host something critical like this, I would need at least 1 active + 1 failover + 3/2/1 backups. I won't be f*k up if one provider just go busted.

    OP if you are going the self-hosted route, consider having at least one automatic backup to an off-site location, or you will end up in a very really funny situation exactly as describe by @BlaZe :D

    Not really. Avoiding any hassles is the goal, not just to not lose all the passwords. They'd just be spending the time setting up a new VPS and restoring from backup instead of jerking off.

    Edit: Actually, no. They'd do a password reset from pornhub, take care of business and then restore the passwords.

  • @TimboJones said: Avoiding any hassles is the goal

    that's why I pay Bitwarden 10$/yr :D the "hassle cost" is much more than 10$/yr for me

  • TimRooTimRoo Member
    edited November 2022

    I run an instance on my LAN that's only accessible via VPN. Seems like the best setup for a single user in terms of the tradeoffs OP mentioned.

    If that's not possible, a very locked down VPS (also only accessible by VPN) might be the next best thing, especially if you've got more VPSs than you know what to do with.

  • @matheny said:

    @TimboJones said: Avoiding any hassles is the goal

    that's why I pay Bitwarden 10$/yr :D the "hassle cost" is much more than 10$/yr for me

    Setting up server using Ansible and cron backup to Backblaze. For 10$ and a little "hassle", I have vault warden, miniflux, wallabag, searx, wireguard,... for a year :D and spin up a new one in 5 minutes if there is any "hassle".

  • melp57melp57 Member
    edited November 2022

    @TimRoo said:
    I run an instance on my LAN that's only accessible via VPN. Seems like the best setup for a single user in terms of the tradeoffs OP mentioned.

    If that's not possible, a very locked down VPS (also only accessible by VPN) might be the next best thing, especially if you've got more VPSs than you know what to do with.

    How do you set up vps to be accessible only through VPN ?
    Edit: I think I found the answer

    Set up a VPS.
    Install a firewall (e.g. ufw )
    Install a VPN service (e.g. openvpn )
    Block all ports via the firewall, but allow SSH and VPN connections.

    Thanked by 2TimRoo Logano
  • @melp57 said:

    @TimRoo said:
    I run an instance on my LAN that's only accessible via VPN. Seems like the best setup for a single user in terms of the tradeoffs OP mentioned.

    If that's not possible, a very locked down VPS (also only accessible by VPN) might be the next best thing, especially if you've got more VPSs than you know what to do with.

    How do you set up vps to be accessible only through VPN ?
    Edit: I think I found the answer

    Set up a VPS.
    Install a firewall (e.g. ufw )
    Install a VPN service (e.g. openvpn )
    Block all ports via the firewall, but allow SSH and VPN connections.

    Yep, that's basically it, with SSH requiring a key. I prefer Wireguard on a non-standard port for this purpose as well since it simply doesn't respond if you try to login incorrectly.

    Thanked by 1melp57
  • Daniel15Daniel15 Veteran
    edited November 2022

    @melp57 said: they often set your vps SSH root password when you order, so you have to make sure you change it! I change it right away.

    sudo is widespread these days, so I usually just completely disable the root user once I've checked that sudo works:

    passwd -d root && passwd -l root
    

    On OpenVZ, you'll also want to regenerate the SSH server certificate/key, to handle bad-quality templates that don't properly regenerate them. Easiest way is completely removing and reinstalling OpenSSH:

    apt remove openssh-server --purge
    apt install openssh-server
    

    @aqua said: Bitwarden doesn't need too many resources.

    Bitwarden needs a bit of resources as it's designed to scale up to tens of thousands or potentially hundreds of thousands of users. For a small home installation with just a few users, Vaultwarden is more than sufficient. It's an alternative implementation of the server-side - completely different app but with a Bitwarden-compatible API, which means it's compatible with the Bitwarden web UI, mobile apps, and browser extensions.

    Bitwarden and Vaultwarden are both great products, they just made different design decisions/tradeoffs :smile:

    @melp57 said: Block all ports via the firewall, but allow SSH and VPN connections.

    You don't even really need firewall rules for this - Just configure your web server (and other server daemons) to only listen on the VPN IP. With most web servers (including Nginx and Apache), you can configure individual sites to only be accessible on particular IPs.

    Install a VPN service (e.g. openvpn )

    I'd recommend WireGuard. It's essentially peer-to-peer rather than client-server. There's no such things as "servers" with WireGuard; it's just peers that communicate to other peers. This means that if you have multiple VPSes, and you add each VPS as a peer in the WireGuard configuration on your computer, you'll be able to directly connect to each VPS over the VPN without relying on any one of the VPSes being a central server.

  • emgemg Veteran

    I use a password manager with the vault stored on my computer. I do not have a shared vault, just the local copy.

    I do not store my passwords and keys on the internet, no matter how secure they may be today. It is as simple as that.

  • FatGrizzlyFatGrizzly Member, Host Rep

    my vaultwarden runs on a rpi4, locally. works fine.

Sign In or Register to comment.