the localtunnel server offline? #93

New Issue

2018-06-28T10:24:37Z

Felix-Chk commented

2018-06-28 10:24:37 +00:00

(Migrated from github.com)

I build a server like this
docker run -d --restart always --name localtunnel --net host defunctzombie/localtunnel-server:latest --port 3000
netstat is already use in 3000

when i try to connnet the server ........

lt --host "http://support.xxx.com:3000" --port 22
tunnel server offline: Request failed with status code 404, retry 1s
tunnel server offline: Request failed with status code 404, retry 1s
tunnel server offline: Request failed with status code 404, retry 1s
tunnel server offline: Request failed with status code 404, retry 1s

What's wrong!!!!!! It doesn't work!
How to fix it ?

I build a server like this `docker run -d --restart always --name localtunnel --net host defunctzombie/localtunnel-server:latest --port 3000` netstat is already use in 3000 when i try to connnet the server ........ ``` lt --host "http://support.xxx.com:3000" --port 22 tunnel server offline: Request failed with status code 404, retry 1s tunnel server offline: Request failed with status code 404, retry 1s tunnel server offline: Request failed with status code 404, retry 1s tunnel server offline: Request failed with status code 404, retry 1s ``` What's wrong!!!!!! It doesn't work! How to fix it ?

defunctzombie commented

2018-07-01 03:48:58 +00:00

(Migrated from github.com)

You need to run with --net host localtunnel server requires the ability to create arbitrary ephemeral tcp sockets to accepts tunnel connections. This is how the protocol works with the localtunnel client.

You need to run with `--net host` localtunnel server requires the ability to create arbitrary ephemeral tcp sockets to accepts tunnel connections. This is how the protocol works with the localtunnel client.

Felix-Chk commented

2018-07-02 06:06:13 +00:00

(Migrated from github.com)

I always run --net host but it doesn't work

I always run `--net host` but it doesn't work

👍 1

gregfr commented

2018-07-20 12:44:29 +00:00

(Migrated from github.com)

I have the same issue....
Using the direct server URL I have:
tunnel server offline: Request failed with status code 404, retry 1s
Using the nginx proxy:
tunnel server offline: Request failed with status code 502, retry 1s
Maybe I missed something in the configuration?
Thanks

I have the same issue.... Using the direct server URL I have: `tunnel server offline: Request failed with status code 404, retry 1s` Using the nginx proxy: `tunnel server offline: Request failed with status code 502, retry 1s` Maybe I missed something in the configuration? Thanks

gregfr commented

2018-07-20 13:00:50 +00:00

(Migrated from github.com)

I found the problem: I'm using a subdomain for the entrypoint so I have to add -- domain ... to the docker run command.

I found the problem: I'm using a subdomain for the entrypoint so I have to add `-- domain ...` to the `docker run` command.

👍 2

unitof commented

2018-09-10 17:54:39 +00:00

(Migrated from github.com)

To clarify what @gregfr figured out: that's the full subdomain you've pointed to your docker's IP address.

The full run command is then

docker run -d --restart always --name localtunnel --net host defunctzombie/localtunnel-server:latest --port 3000 --domain [sub.domain.tld]

…replacing [sub.domain.tld] with your custom subdomain.

To clarify what @gregfr figured out: that's the full subdomain you've pointed to your docker's IP address. The full run command is then ``` docker run -d --restart always --name localtunnel --net host defunctzombie/localtunnel-server:latest --port 3000 --domain [sub.domain.tld] ``` …replacing `[sub.domain.tld]` with your custom subdomain.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: hoelee/server#93