Comment

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

Sort:hotnew top

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