server icon indicating copy to clipboard operation
server copied to clipboard

404 and client crashes after a few seconds after connect

Open iiko1c opened this issue 5 years ago • 9 comments

"When I use my own localtunnel server it shows "404". But when I use the default localtunnel.me it works perfectly.

Also i noticed. If i access my LT server, i'm able to access http://my-lt-server.example.com:47777/api/status but http://my-lt-server.example.com:47777/api/tunnels/[tunnel-id]/status will return a Not Found page.

I just found out after running tunnel from my dev machine.

lt --host http://my-lt-server.example.com:47777 --port 80

It crashes after a few seconds. But it doesnt show any error. Is there a way to find the error?"

iiko1c avatar Oct 14 '19 10:10 iiko1c

I have the same problem. I tried as a dependency and it doesn't show errors either.

guillermojmc avatar Nov 04 '19 19:11 guillermojmc

same issue here

bogdanrn avatar Dec 12 '19 12:12 bogdanrn

same issue

nvthuong1996 avatar Dec 16 '19 10:12 nvthuong1996

same

Fatflo avatar Jan 13 '20 01:01 Fatflo

Same issue for me as well

mquekel avatar Feb 25 '20 13:02 mquekel

Likely your server doesn't have high TCP ports open on the firewall for the tunnel connections. Start the server with debug enabled to see more info:

DEBUG=* node -r esm bin/server --host http://myhosthere.com --port xxxx

mikericks80 avatar Aug 06 '20 23:08 mikericks80

After running this:

DEBUG=* node -r esm bin/server --port 9000 --domain <sub.domain.tld>

Got this

  koa-router defined route HEAD,GET /api/status +0ms
  koa-router defined route HEAD,GET /api/tunnels/:id/status +3ms
  koa:application use dispatch +0ms
  koa:application use allowedMethods +0ms
  koa:application use - +1ms
  koa:application use - +0ms
  localtunnel server listening on port: 9000 +0ms
  koa-router GET / +0ms
  koa-router test /api/status /^\/api\/status(?:\/(?=$))?$/i +0ms
  koa-router test /api/tunnels/:id/status /^\/api\/tunnels\/((?:[^\/]+?))\/status(?:\/(?=$))?$/i +1ms
  localtunnel:server making new client with id spotty-chipmunk-40 +0ms
  lt:TunnelAgent[spotty-chipmunk-40] tcp server listening on port: 42659 +0ms
  lt:ClientManager removing client: spotty-chipmunk-40 +0ms
  lt:TunnelAgent[spotty-chipmunk-40] closed tcp socket +1s
  lt:TunnelAgent[spotty-chipmunk-40] closed tcp socket +0ms

knockshore avatar Apr 27 '21 07:04 knockshore

Thanks for the suggestion. It seems the host server is behind the firewall and the lt client was not able to connect to the lt server created randomly port.

knockshore avatar Apr 27 '21 07:04 knockshore

Hello! Anyone found the solution to this problem?

WINOFFRG avatar Mar 01 '22 11:03 WINOFFRG