Recommendations for closed NAT bypass methods

Submitted ⁨⁨4⁩ ⁨days⁩ ago⁩ by ⁨Cartilage@slrpnk.net⁩ to ⁨selfhosting@slrpnk.net⁩

I’m behind a closed NAT and my ISP won’t cooperate.

Is renting a VPS for SSH tunnels a good idea? Looking for a solution for tunneling out of the NAT with support for non-https ports.

source

Comments

Sort:hotnew top

xyro@morbier.foo ⁨4⁩ ⁨days⁩ ago
Yes, I would recommend to setup a wireguard tunnel between your vps and homeserver.

Then you can just expose whatever port your want on the VPS and forward the traffic to your server. I use nginx to forward the traffic to my server, but there is different reverse-proxy you could use.

source
CompactFlax@discuss.tchncs.de ⁨3⁩ ⁨days⁩ ago
Tailscale also may be an option.

source
anytimesoon@piefed.social ⁨3⁩ ⁨days⁩ ago
Pangolin can do exactly all of this, but it does require a vps

source
- Cartilage@slrpnk.net ⁨3⁩ ⁨days⁩ ago
  How well does it run on a shared CPU VPS with the recommended specs?
  
  source
  - anytimesoon@piefed.social ⁨2⁩ ⁨days⁩ ago
    Works fine for me. Havent had any issues at all. I’m only running a few services for me and my gf.
    
    There is one public facing service hosted on the same vps as the pangolin stack and that gets a fair bit of traffic, but everything runs fine
    
    source
BastingChemina@slrpnk.net ⁨3⁩ ⁨days⁩ ago
If it’s just for your own usage tailscale is probably the easiest solution. It create a tunnel between you and your server.

If you want to share your services with friends and family and not everyone want to use tailscale then I’m using pangolin and in quite happy with it.

source
sylver_dragon@lemmy.world ⁨3⁩ ⁨days⁩ ago
I’m behind CGNAT with my ISP. I have a VPS which I use to tunnel traffic back to my home network with Wireguard. That gets terminated on the outside of my router and specific ports get forward in from there. Works well enough.

source