Localtunnel is not setting up the requested subdomain from the command 'lt --port 4000 --subdomain xyz'
See original GitHub issueI have been trying to set the subdomain in localtunnel, but it keeps throwing me different subdomains.
Port number is 4000 and it’s running.
The command which I used : lt --port 4000 --subdomain xyz
(I changed subdomain name for the security reason).
Where am I doing wrong?
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
Top Results From Across the Web
Localtunnel is not setting up the requested subdomain from ...
Port number is 4000 and it's running. The command which I used : lt --port 4000 --subdomain xyz (I changed subdomain name for...
Read more >Top 4 BEST Ngrok Alternatives In 2023 - Software Testing Help
Comparison Of Ngrok And Its Alternatives; #1) Localtunnel; #2) Serveo ... One time subdomain setup which is tied to email address is required...
Read more >Kogam22/server - Buttons - Heroku Elements
The localtunnel server is now running and waiting for client requests on port 1234. You will most likely want to set up a...
Read more >Localtunnel: Expose Yourself - Morioh
When localtunnel is installed globally, just use the lt command to start the ... --subdomain request a named subdomain on the localtunnel server...
Read more >Running a Reverse Proxy Server with Localtunnel - Medium
Ensure that your team does not accidentally (or intentionally) steal someone else's subdomain. Setup Nginx. Configure nginx using the following files from the ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
[ISSUE]: REQUESTED SUBDOMAIN NOT WORKING AFTER ONCE
check the running daemon in your server. Chances are that when you exit the tunnel or terminal, the tunnel thread becomes a ZOMBIE daemon . Step 1: use [ps aux] to view all daemon Step2: identify the zombie local tunnel thread (example: node /usr/local/bin/lt -p 8000 -s urdomain) Step3: kill with it’s pid [kill -9 [pid]] Step4: check with ps aux once again, it must be disappeared Step5: request your favourite sub-domain once again . it should be good to go now. if not kindly let me know.
I solved it this way.
The problem: Once you make your subdomain request, and then terminate it with Ctrl+c. It will terminate on the terminal but, the task still runs on the background. I solved it by going to task manager, and terminating all task that involve “HOST”. After that, make your request again for subdomain. i.e, lt --port 3002 --subdomain mysubdomain