localtunnel: I got 504 Gateway Time-out Error

I installed lt today and I keep getting connection errors over and over. If the main suggestion is to use another project, would it not be better to just put this “advice” in the main page so people don’t waste their time?? I understand this is open source etc, but if nobody is taking care of this project this should be made aware to the people that are trying to use it.

Yes, ngrock is the way to go. There doesn’t seem to be a workaround for localtunnel.

You can try to use ngrok instead

I think this may be related to a change in OS X 10.11 El Capitan.

I have identical web stacks running on two machines: one with Yosemite, the other with El Capitan. I just tried lt --port 5000 on both. The Yosemite machine works fine and the El Capitan machine doesn’t get back to the web server running on port 5000. I’ve checked for firewall - none.

I know there are other dev tool breakages on El Capitan so I’m skeptical. Can anyone confirm whether they’ve used lt successfully on OS X 10.11?

Thanks.

@JerryGreen I don’t know why people had this issue, but in my case it was becouse of wrong ip adress. Localtunnel works like this (simplified) :

• You have localtunnel server generally localtunnel.me, but also you can find repo on github and run your own
• localtunnel client, whitch is a node process on your local machine, that:

1. opens several (i.e 10) connections to localtunnel server
2. when localtunnel-server receives a request, it uses one of opened connections from client to pipe the request, then local client connects to your local app, get response, and returns it to server

• Then server send response to you.

If localtunnel client cannot connet to localtunnel-server you will receive an error after lt ...., but when locatunnel client cannot connect to your app for some reason, you will receive an timeout in browser.

I’m not an expert in networking, but there is difference between ip localhost whitch is 127.0.0.1 and ip of your network card in local network, in my case 192.168.8.109.

To sum up, just make sure that you are using correct ip address.