4 ms·

I really like ngrok, but I keep bumping into a limitation: if I leave a development tunnel open from one machine, there is no way to shut it down remotely and o

• erikschoster 5y ago
  That would be a handy thing to do. A workaround could be to have a raspberry pi or similar as your ssh access point to a local network via ngrok, with your main ngrok service running on another machine on the local network in screen or tmux. Then just ssh into the raspberry pi, connect to the machine running the main ngrok service, drop into the session and reconfigure as you like?
• anderspitman 5y ago
  Maintainer of the list here. Take a look at my boringproxy project. Once you have the clients running on each machine, all the tunnels can be managed through a web UI on the server. With a little elbow grease[0], you can also SSH into any of the clients (as long as they have sshd running). [0]: https://forum.indiebits.io/t/how-to-forward-ssh-port-example-just-in-time-feature-request/56/5?u=anders https://forum.indiebits.io/t/how-to-forward-ssh-port-example...
• joemclarke 5y ago
  There is a beta feature you can enable to shutdown any open tunnel from the dashboard. It’s under tunnel agent, status. I use this every day because I always forget to shut down the agent on my home computer before going to the office.