cross-posted from: https://feddit.de/post/10554932
I am looking something to connect to my server from outside my local network.
I am on a shared IP and my ISP doesn’t have port forwarding.
cross-posted from: https://feddit.de/post/10554932
I am looking something to connect to my server from outside my local network.
I am on a shared IP and my ISP doesn’t have port forwarding.
I can recommend rathole ( https://github.com/rapiz1/rathole ).
All it does is port forwarding. Easy to configure, easy to reason about, easy to dockerise.
If you need reverse proxying, you have to set that up either on the public server, or on local infra (chances are, you already have reverse proxy locally so rathole just needs to forward 80/443).
If its only for personal access (ie, you dont want services actually accessible by the internet) i can recommend tailscale for that. Its an auto-configuring wireguard VPN whose main selling point is NAT traversal. Very easy to set up, and very reliable.
Why rathole and not ssh tunneling? The latter exposes only one port (that you are already exposing anyway) while the former requires an additional port.
What is the actual benefit of rathole? I an asking genuinely.
Hmm, fair.
I liked it cause i could dockerise it next to nginx and do SNI forwarding.
It had obvious and declarative config, which helped me get a redundant tunnel set up. Its great at auto-reconnecting.
I have never used ssh tunnels. Maybe its just as easy as using rathole. Learning ssh tunnels might have been a better path for me.
But rathole clicked, has been rock solid with 0 tinkering or tweaking, the config files make sense, its easy to in a docker container…
So, i cant really answer your question.
Fair, setting up ssh tunnels with autoreconnect and such is indeed more complex.
I think 1 big advantage is that rathole can work over a websocket connection.
So, if obfiscating, having to go via HTTP proxies, or whatever… rathole will still work.
This is a great reason, I didn’t know, but its interesting.