When connection crashes, can no longer use that subdomain

I understand that good work is being done on this library to help improve reliability. I wanted to bring up another issue that may be related in an adjacent way. I’m also curious if anyone else is having this issue.

My connection frequently disconnects, but I then can’t use that same subdomain… I don’t mind having to restart localtunnel every now and then, but losing access to that subdomain is pretty frustrating.

For example, I use mydomain as the subdomain on port 3000, it crashes, and when I run lt --subdomain mydomain --port 3000 again, it generates the random characters. I then have to use something like mydomain1, and update the server address on every single sensor I have (which send data over a cellular connection to my rails server), which is definitely frustrating.

Has anyone else had this issue?

Is there any way to kill all instances of localtunnel if there are instances running…?

[defunctzombie]

I’ve deployed a new server backend that should resolve this issue. If your client is disconnected (or dies) then the subdomain will be available again within a second.

[saeta-eth]

@defunctzombie I use nodemon to automatically restart my node server and, sometimes, it also happens when I make some changes in my application.

Localtunnel logs: /usr/local/lib/node_modules/localtunnel/bin/client:58 throw err; ^ Error: connection refused: localtunnel.me:36312 (check your firewall settings) at Socket.<anonymous> (/usr/local/lib/node_modules/localtunnel/lib/TunnelCluster.js:47:32) at Socket.emit (events.js:127:13) at emitErrorNT (internal/streams/destroy.js:64:8) at process._tickCallback (internal/process/next_tick.js:114:19)

Then, I try to restart localtunnel but it gives me a different URL and ignores my subdomain.