This is an automated archive made by the Lemmit Bot.
The original was posted on /r/selfhosted by /u/MoshiMotsu on 2025-03-03 22:31:47+00:00.
I've always wanted to dip my toes into the world of self-hosting, but something I'd really like to do is be able to access my self-hosted servers from outside my home LAN. One way I understand you can do this is through something like a VPN, but something else I'd really like to pull of is give my services some sort of public-facing URL, so that, for example, members of my family could use my Jellyfin instance, or friends of mine could set up their own Bitwardens on my Vaultwarden instance. I don't think we have to reinvent the wheel when it comes to self-hosting, and I think a big strength of the paradigm is in accepting some centralization of control, but only because you personally know the person helping you host your personal digital infrastructure. It just becomes a matter of specialization, really.
One issue, however, is the idea that some technical or physical mishap could flush my entire server, and, if I've chosen to let others into my network, everyone else's data with it. (The big fear here being something like a friend's password maanger getting wiped.) Say I have a Vaultwarden instance, and then there's just a flood on a different floor and the machine that was hosting it is bricked. As far as I know, so too is all my data.
I also figure, however, that this isn't a problem unique to self-hosting. I'm sure other cloud provider's have to deal with this risk, too. So, I wanted to ask; do any of you have experience "duplicating" servers so that it functionally exists and backs itself up in multiple locations? Is it set up in such a way that, if one were to vanish, the users of your instances wouldn't really notice? Just trying to get more information before I really decide to take the plunge!