Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`--subdomain` option does not always work
See original GitHub issueI’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.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:61
- Comments:82 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
👍 Same problem here and I am depending on it for local development debugging with a third party application.
This issue still exists. I was running a server with a subdomain before my PC unexpectedly went off. After powering it back on, i can no longer use the subdomain i was previously using.
When i try a new subdomain, it works but can’t use the old one. Seems like the subdomain was not explicitly unassigned in the localtunnel server after the unexpected disconnection.