Other ports for http (8086 example)

[Mariusz]

Hello

Is it possible to share port other than 80 ? I ask because I have RaspCTL running on port 8086:

http://s13.postimg.org/pod3vjoo7/lt3.png

Then I run localtunnel:

root@raspberrypi:/home/pi# localtunnel-beta -n testinglt 8086

  Thanks for trying localtunnel v2 beta!

  Source code: https://github.com/progrium/localtunnel

  Donate: http://j.mp/donate-localtunnel

  Port 8086 is now accessible from http://testinglt.v2.localtunnel.com ...

Then I try to open it:

http://s16.postimg.org/gf75tci3p/lt4.png

So, not working with 8086 ? 

[Paulo Borges]

The server runs locally in the specified port (8086), but it is exposed in port 80 by localtunnel. Try again without ":8086" at the end of the url in your browser.

--
You received this message because you are subscribed to the Google Groups "localtunnel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to localtunnel...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Mariusz]

The respanse if just http://testinglt.v2.localtunnel.com is the same like  http://testinglt.v2.localtunnel.com:8086 (service is running - localtunnel connection created when I tried it, and port 80 woks fine all the time). Maybe RaspCTL uses / based in some individual http server / parallel to apache2, I do not know. But it doesn't work with RaspCTL on 8086 port.

[Jeff Lindsay]

Can you prove you have something listening on 8086?

--
Jeff Lindsay
http://progrium.com

[Mariusz]

Hello again.

I'm sure some www server is running and working on port 8086 bacause I can simply enter page of RaspCTL from LAN side on port 8086 (192.168.1.110:8086). I'm only not sure if it is the same apache2 server that is working on port 80. From LAN I can enter both 192.168.1.110 and 192.168.1.110:8086 without any problems. I can also share 80 port via localtunnel v2 without any problems. Problems are only when I try to share 8086 port (result is 8086 is never accesible from WAN and always accesible from LAN). No problem with sharing port 80.

Best regards

Mariusz

[Jeff Lindsay]

Try pulling the latest from master in Git. We've been experimenting with Windows a little and noticed our code tries to connect to the local server with 0.0.0.0, but that didn't work in Windows. Changing it to 127.0.0.1 does work, though I can imagine edge cases where this won't work for people that bind specifically to a non-loopback interface. Anyway, point is, it might help in your situation.