3 ms·
Personally I would rather just use "ssh -R", the built in remote port forwarding. You either need to flip a setting on the server to allow listening on an inte
by tedchs 13y ago
Personally I would rather just use "ssh -R", the built in remote port forwarding. You either need to flip a setting on the server to allow listening on an interface besides localhost, or configure Nginx/etc as a reverse proxy.
For example:
ssh -f -N -q -R 2222:localhost:22 my_name@remote.example.com
Decent writeup here:
http://www.noah.org/wiki/SSH_tunnel http://www.noah.org/wiki/SSH_tunnel
- thedufer 13y agoThat's what I've used in the past, but its more complicated to set up ("You either need to flip a setting on the server to allow listening on an interface besides localhost, or configure Nginx/etc as a reverse proxy." is not trivial for most). It also requires a server with a static IP to ssh to.
- tedchs 13y agoYes. This is cold hearted, but I would suggest that for those for whom this is too hard, they should reconsider exposing their machines and code directly to the public Internet.
- shtylman 13y agoWhy should they reconsider it? Someone that just got into development and might want to show their friends or family something they are hacking away on. According to you they now need to learn about VPS, some random nginx settings or other SSH nonsense and meet some arbitrary "minimal" criteria you have decided upon because that is how you would do it. I think you should reconsider your acceptance of people that don't share your same technological expertise.