Localtunnel: Tunnel crashes randomly after 20-30 Minutes

[Scarwolf]

abc@bcd-GL MINGW64 ~
$ lt -l grumberg.app -p 80
your url is: https://zsmhwraqtc.localtunnel.me
C:\Users\abc\AppData\Roaming\npm\node_modules\localtunnel\bin\client:58
        throw err;
        ^

Error: connection refused: localtunnel.me:33399 (check your firewall settings)
    at Socket.<anonymous> (C:\Users\abc\AppData\Roaming\npm\node_modules\localtunnel\lib\TunnelCluster.js:47:32)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:191:7)
    at emitErrorNT (net.js:1295:8)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)

Any idea?

[Kosmonaft]

I'm having the same issue

[buckett]

Happening here too, same error different port number. Stack trace is the same. Version 1.8.3.

[hoover456]

Getting the same error.

[igorstimoli]

Got the same error

[D3X]

Same here. Running on a macOS. A _slightly_ different stack trace.

your url is: https://<redacted>.localtunnel.me
/usr/local/lib/node_modules/localtunnel/bin/client:58
        throw err;
        ^

Error: connection refused: localtunnel.me:45733 (check your firewall settings)
    at Socket.<anonymous> (/usr/local/lib/node_modules/localtunnel/lib/TunnelCluster.js:47:32)
    at emitOne (events.js:115:13)
    at Socket.emit (events.js:210:7)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)

[k9t9]

Same issue

[gaetansenn]

Hi guys,

Any news about that issue ?

[k9t9]

Somehow i have a feeling it has to do with dns queries or changes from isp

[devhyunjae]

Same here

[defunctzombie]

The service is not the most reliable and such crashes will sometimes happen. Localtunnel is a development focused tool meant for use over short bursts of time rather than long hosting periods.

[D3X]

@defunctzombie it happens after a few minutes, sometimes even shorter. Also, the crash is caused by an uncaught exception. It should at least be handled gracefully. Of course, ideally, it would recover and reconnect.

[kirillshevch]

@Scarwolf @hoover456 @igorstimoli @gaetansenn @D3X
As a hotfix you can use localtunnel-restarter

[christroutner]

I'm seeing this same issue with the latest code.