IssueRaiser

`--subdomain` option does not always work

I've noticed that _in some cases_ when a user starts a localtunnel client - then exits it (via ctrl + c) - the named tunnel is not returned. Launching the client again and requesting the same subdomain results in the user being assigned a random name instead. Run the client as usual and request a custom domain. ``` lt --subdomain nice-donkey-20 --port 8000 ``` Then run the client again - requesting the domain and sometimes you are not given the same domain. This behavior has come up in the past and requires looking into the localtunnel/server logic for connection count tracking.

Posted by defunctzombie on May 16, 2018, 8:06 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments

github (Sysadmin)

`--subdomain` option does not always work

defunctzombieMay 16, 2018, 8:06 PM

I've noticed that _in some cases_ when a user starts a localtunnel client - then exits it (via ctrl + c) - the named tunnel is not returned. Launching the client again and requesting the same subdomain results in the user being assigned a random name instead. Run the client as usual and request a custom domain. ``` lt --subdomain nice-donkey-20 --port 8000 ``` Then run the client again - requesting the domain and sometimes you are not given the same domain. This behavior has come up in the past and requires looking into the localtunnel/server logic for connection count tracking.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue