Comment

ptz@dubvee.org ⁨7⁩ ⁨months⁩ ago

Are any of your services public facing? If so, you might want to make the VPS your reverse proxy and VPN server and have your stack at your friend’s house connect to the cloud server - reverse proxy in the VPS would connect back over the VPN to the equipment at your friend’s house.

This would prevent your friend from having to open ports in their router and from exposing their IP to the world (beyond their normal traffic, that is).

Plus, it would allow you to VPN-in to manage as well as have a “kill switch” should you need it (cyberattack, etc)

source

Sort:hotnew top

palitu@aussie.zone ⁨7⁩ ⁨months⁩ ago
Are any of your services public facing? Yes. i think that is like a “bastion” server, or something like that. good idea. I expect that i can get more-or-less free VPS, and just run the NPM and tailscale or something there.

I would not run any of the *arrs on a network that is not yours Good thought, i dont think i would need it whilst i am away anyway.

And definitely make sure your friend knows yep, responsible hosting :D

thanks for the thoughts.

source
- lemmyvore@feddit.nl ⁨7⁩ ⁨months⁩ ago
  Well not free VPS (if you want it to be semi-reliable) but within $3-5/mo.
  
  You don’t need to run your NPM on the VPS (although it does make things easier). You can:
  
  Forward the whole interface to your server and just sort things out there. Downside: all visitors will appear to have the VPS’s IP.
  
  Do DNAT/SNAT one the VPS to make the forwarded connections appear to have the original remote IP instead of the VPS. Downside: a bit more complicated (a few firewall rules).
  
  Install a very basic nginx proxy on the VPS whose whole job is to put the original remote IP in a HTTP header, and on your server NPM use that header. Downside: you have to terminate and restart the TLS connection on the VPS.
  
  Use SSH tunnels instead of VPN tunnels. A VPN forwards a whole interface, a SSH tunnel forwards a single port. You will still have to deal with the IP thing. Additional downside is that it only works for TCP, it’s not worth bothering to forward UDP. But it’s much simpler to set up than a VPN, basically one command (or autossh to maintain it automatically).
  
  source
atzanteol@sh.itjust.works ⁨7⁩ ⁨months⁩ ago

This would prevent your friend from having to open ports in their router and from exposing their IP to the world (beyond their normal traffic, that is).

Their IP address is already “exposed to the world.” I keep seeing people recommending this pattern in this community for the same reason. But I genuinely don’t understand it. It sounds like one of those VPN ads frankly.

Your IP address is not private.

Frankly I would mothball the servers and move everything to the cloud rather than use a friend’s resources. You retain control over the environment and don’t need to worry about somebody unplugging your computer to vacuum.

source
- ptz@dubvee.org ⁨7⁩ ⁨months⁩ ago
  
  Their IP address is already “exposed to the world.” I keep seeing people recommending this pattern in this community for the same reason. But I genuinely don’t understand it. It sounds like one of those VPN ads frankly.
  
  Your IP address is not private.
  
  I did state “beyond their normal traffic”. And you do realize there’s a significant difference between exposing your IP as a client and exposing your IP as one that has servers hosted behind it, right? It’s not about protecting that or keeping it secret. It’s about not putting a target on their friend’s IP address for all the bots and script kiddies to hit.
  
  source
  - atzanteol@sh.itjust.works ⁨7⁩ ⁨months⁩ ago
    
    And you do realize there’s a significant difference between exposing your IP as a client and exposing your IP as one that has servers hosted behind it, right?
    
    No, there isn’t. Bots scan indiscriminately. And script kiddies will still attack your servers running in their network, just via your proxy.
    
    source
- lemmyvore@feddit.nl ⁨7⁩ ⁨months⁩ ago
  With this pattern you open up an outgoing connection to the VPS, establish a two-way tunnel, and the VPS will use it to forward connections to you.
  
  People who use your services this way see the VPS’s public IP, yours is hidden from them.
  
  Sure, you still have a public IP while doing this but (a) only the VPS can see it and (b) you really don’t have to open ports on it and in fact may not even be reachable through it if it’s doing NAT.
  
  source
  - atzanteol@sh.itjust.works ⁨7⁩ ⁨months⁩ ago
    What benefit do you think the vps provides though?
    
    source
    lemmyvore@feddit.nl ⁨7⁩ ⁨months⁩ ago
    The most common ones:
    
    Hiding your IP when you open services to the internet. Some people live in suburbs or towns where their IP can pinpoint their house almost perfectly.
    
    Breaking out of ISP NAT (aka carrier NAT / CGNAT), where clients can’t open connections to your public IP.
    
    source
    -> View More Comments