• 0 Posts
  • 41 Comments
Joined 7 days ago
cake
Cake day: February 5th, 2025

help-circle








  • The entire point of selfhost is to host private services not available to the public. By literal definition, that’s allowing only local traffic to connect to your services. It’s infinitely more secure. A VPN allows you to extend those services over the clearnet to authorized devices via virtualized networks. You don’t have to worry about messing with inbound/outbound ports, or worrying about software failure or misconfigurations accidentally exposing you to the clearnet. You don’t have to worry about DDoS, or abuse. Being attacked? Bring down your VPN and that completely shuts down your issue. Your network is completely unreachable by anyone but a local host.

    There’s simply no room for an argument. VPN is objectively better in all possible situations.





  • You may say that’s a good practice to separate things

    You’re missing the point. VPN isn’t about separating anything… I’m not even sure what you mean by that. VPN is the accepted practice here. Unquestionably. You create private services, and for security you only expose them to the least amount of people possible. You authenticate via VPN connections. You only have to maintain a single database of users to access any number of services, even tens of thousands.

    OP is specifically talking about hosting local content that they want to protect. VPN is the solution here.








  • If somebody needs to have services accessible by someone else besides him, that service can’t be behind a VPN

    Again, this is the reason VPNs exist. If that person needs access, then setup Wireguard…

    It’s like saying you don’t need a front gate with an access code because then you would have to give out your own access code. But I mean, the lock has the ability to setup more access codes. And you’re saying the only viable option is the leave the gate open and hire a guard to manage access. It’s just… Weird and wrong.