Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

new connection on port: banana #10

Closed
CWSpear opened this issue May 19, 2014 · 1 comment
Closed

new connection on port: banana #10

CWSpear opened this issue May 19, 2014 · 1 comment

Comments

@CWSpear
Copy link

CWSpear commented May 19, 2014

I was having issues setting it up on my server, so I started testing locally and got similar results.

I cloned localtunnel-server locally and ran this command:

env DEBUG="localtunnel*" bin/server --port 1234

Then I ran this command in another shell:

 lt --host http://localhost:1234 --port 8000 --subdomain banana

(I have a Laravel app running on port 8000 and lt --port 8000 works going through localtunnel.me.)

The client says my url is http://banana.localhost:1234 and if I go there (I added banana.localhost to my hosts), then I get the main index of what's at localtunnel.me.

The server debug output says a bunch of stuff about connection to port "banana" when I connect the client.

  localtunnel server listening on port: 1234 +0ms
  localtunnel-server request /banana +0ms
  localtunnel-server making new client with id banana +11ms
  localtunnel-server tcp server listening on port: 50814 +1ms
  localtunnel-server new connection on port: banana +12ms
  localtunnel-server new connection on port: banana +0ms
  localtunnel-server new connection on port: banana +1ms
  localtunnel-server new connection on port: banana +0ms
  localtunnel-server new connection on port: banana +0ms
  localtunnel-server new connection on port: banana +1ms
  localtunnel-server new connection on port: banana +0ms
  localtunnel-server new connection on port: banana +0ms
  localtunnel-server new connection on port: banana +0ms
  localtunnel-server new connection on port: banana +1ms
  localtunnel-server request / +8s
  localtunnel-server request /static/541f20/css/style.css +496ms
  localtunnel-server request /static/99735c/css/grid.css +1ms
  localtunnel-server request /static/0f1bee/css/widgets.css +1ms
  localtunnel-server request /static/21e1e0/js/index.js +1ms
  localtunnel-server request /engine.io/?EIO=2&transport=websocket&sid=6RlMHqlk_JJVrx9UAAAA +216ms

This is more or less what was happening on my server, too, except I was having issues with the maybe_bounce function. If I forced it to return false, then my experience on the server is the same as that.

@CWSpear CWSpear mentioned this issue May 19, 2014
@defunctzombie
Copy link
Contributor

I think the issues here have been resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants