Options to access a host from behind NAT and firewall
Here and later, ‘host’ is the thingy hidden behind NAT.
- Mullvad allows forwarding ports. Then the host connects to mullvad, and I connect to its forwarded ports through public mullvad IP
- forwarded port is dynamically generated
- the host has to connect to the same exact server with the forwarded port
- anderspitman/awesome-tunneling: List of ngrok alternatives and other ngrok-like tunneling software and services. Focus on self-hosting.
- “For most people, I currently recommend CloudFlare Tunnel.”
- Cloudflare Tunnel · Cloudflare Zero Trust docs
- Had an acc there
- Moved one domain there
- Set up
cloudflared
on the server- Really easy install
- No luck
- Oh wait it works!
- Sometimes
- May debug later
- https://boringproxy.io/
- needs 80/445, wasn’t able to do non-standard ports on an already existing server w/ certs through dir
- didn’t get it to work :(
- https://tunnel.pyjam.as
- worked like a charm!
- Quick etc., but using someone else’s domain is not what I need
- fatedier/frp: A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet.
- Worked immediately for SSH
- Worked almost immediately for HTTP (no ‘S’, but that was the issue w/ boringproxy - acme errors)
- Doesn’t force you to use HTTPS
- Neat intuitive documented config and config files!
- Really neat dashboard with statistics etc!
Nel mezzo del deserto posso dire tutto quello che voglio.
comments powered by Disqus