OsX/Windows: Unable to initiate connection to 127.0.0.1:8080 about ngrok HOT 5 CLOSED

Are you running a webserver on port 8080? You need to tell ngrok which port your local web server is running on. The port 8080 used in the documentation is just an example.

For example, if I'm developing a web service that's running on port 80 (like apache+php), I would run ngrok as follows:

./ngrok 80

Please send me a gist of the cygwin terminal error, I'm interested in fixing that.

from ngrok.

how dumb of me...
Somehow I didn't realize ngrok was tunneling to a unique port. I guess I was focused on my own need which is the equivalent of ssh -D, i.e. a dynamic tunnel that can support request on any port.
I thought the localport was to communicate with a local ngrok listener process that would then redirect on demand.

Anyway, that's pretty useful stuff.
You may not have thought of this you case, but FYI the fiber optical provider in the country I live don't even bother to provide IP address anymore. (I mean not even a dynamic IP). They most probably do big scale NAT.
They say "there isn't enough IPv4 addresses, we can't provide one unless you pay for entreprise level service"
So there isn't a convenient way to host service anymore.
ngrok comes very handy to circumvent that problem.

here's the gist of the cygwin crash: https://gist.github.com/nodje/6373558

from ngrok.

I've opened a separate issue for the cygwin crash.

I'm interested in your other use case. If I understand it correctly, you basically want to run a public SOCKS server into your network? So that there's a public port you can connect to and that will allow you to initiate a TCP connection via SOCKS to any address:port on your local network?

The next version of ngrok will support running multiple tunnels simultaneously, which (if I've understood you correctly) won't exactly get you everything you want, but it should be closer. For now, of course, you can always run multiple ngrok processes to get multiple tunnels.

from ngrok.

I guess running multiple tunnels simultaneously would do for my needs, it would be a replacement for port opening on a router - which is now useless for me since I don't have a public IP anymore.

If I could open an ssh connection on a specified port through ngrok, I would probably get an ssh -D equivalent behavior, woudn't I ?

from ngrok.

Yes, I think you would. And you can tunnel ssh connections (or any other protocol) by using ngrok in TCP mode.

ngrok -proto tcp 22

from ngrok.