Ngrok: kill a tunnel registered on a reserved subdomain

[AshHeskes]

Is there any way to force the closing of a tunnel associated to a reserved subdomain within my account.

There seems to be an issue with with the node ngrok lib that doesn't correctly kill a tunnel when the program using it unexpectedly crashes. This causes the tunnel to remain open according to ngrok so trying to connect a new tunnel on that subdomain is impossible.

I understand this may be impossible to deal with for general subdomains issued by ngrok. However I'm using a reserved subdomain on a payed account. It would be good if I had the power to force kill any active tunnels on that subdomain.

[inconshreveable]

This isn't a supported operation at the moment, but I think it's a reasonable one to support in the future.

If you kill the ngrok client process, that should kill all associated tunnels that are running on it.

[AshHeskes]

The ngrok process is terminated, but it still says the subdomain is already registered when trying to reinitiate ngrok.

I've had this issue a few times before, and there is (? was) an open issue for it at the node ngrok repo.

Still, it would be a useful feature.

[inconshreveable]

Does the 'subdomain is already registered' problem persist permanently, or does it go away after a short amount of time?

[jozanza]

+1 I'm also having an issue with this.

[inconshreveable]

I'm working more on a root cause fix to stop tunnels from "hanging" and remaining open after you've closed them. Still keeping this open for the future.

[msolomonTMG]

+1

[jakeleboeuf]

+1

[ericraio]

+1

[docksteaderluke]

+1

[wassupnari]

+1

[cloud9coding]

+1

[RubenCordeiro]

+1

[cyogrant]

+1

[inconshreveable]

Yep, working on a fix for this right now. Fix will address another issue that causes a tunnel to 'hang open' for ~5 minutes after it was intentionally closed.

[inconshreveable]

The latest cause of tunnels hanging open has been resolved. Apologies for the problems with the service. I'll leave this issue open since there's still no way to "force close" a tunnel, but the chances that you'll need to do that are now much more rare.

[mrnnn]

Still have detached sessions referring to my home ip while at work. 2 sessions in fact, even though i'm only allowed one. not sure how that happened :-). Anyway, it'd be nice to be able to detach them if you know the auth token & secret, or through the ngrok client portal.

[inconshreveable]

no longer an issue in the hosted service

[ZackBurtPoncho]

How do we programmatically kill detached sessions in order to deal with this error?

[Hedgehogking]

+1

[KharitonOff]

I can't restart my ngrok connection:

Tunnel session failed: Your account 'XYZ' is limited to 1 simultaneous ngrok client session.
Active ngrok client sessions in region 'us':
  - 414c40ed9afc1756ffa78f2d32fc3617 (155.56.44.134:63846)

I've got this issue using [email protected]

[juergen-vogel]

@KharitonOff You can fix it by setting your authcode once again. When you're logged in you can find it here: https://dashboard.ngrok.com/get-started

$ ./ngrok authtoken YOUR-TOKEN

[jonjaques]

killall ngrok

[sjordan1975]

Having issue today and suggest "You can fix it by setting your authcode once again. When you're logged in you can find it here: https://dashboard.ngrok.com/get-started" did not work

[theo-bittencourt]

Facing same issue now.
Refreshing authcode didn't work.

[vladich]

@KharitonOff You can fix it by setting your authcode once again. When you're logged in you can find it here: https://dashboard.ngrok.com/get-started

$ ./ngrok authtoken YOUR-TOKEN

this doesn't work

[synth]

Experiencing same issue. We tried resetting authtoken and no dice. It would be great if there was a way to kill the tunnel from the website.

[aszalacinski]

Experiencing same issue as well.

[ryanckulp]

i shared this on another related issue but we baked our own solution here:
https://blog.fomo.com/remotely-kill-ngrok-session/

[gavinsmith]

+1. Resetting token doesn't work, no running processes on the client, it's just perma-reserved on my account. No way to kill it from the web UI or CLI tool.

[chris-rowe]

+1 on what @gavinsmith said above. Nothing is terminating the tunnel making ngrok unusable on my system

[airtwo]

+1

[PlanetHackers-YT]

Any one found a solution for this
Tunnel session failed: Your account 'XYZ' is limited to 1 simultaneous ngrok client session.
Active ngrok client sessions in region 'us':

• 414c40ed9afc1756ffa78f2d32fc3617 (155.56.44.134:63846)

[joelbernstein]

Why is this closed? There's still no way to kill a tunnel registered on a reserved subdomain. Please don't close tickets with genuine unfixed issues in! People have been complaining about this for SIX YEARS. We pay for the Ngrok service. This isn't good enough. The suggested "fix" of resetting the authtoken does nothing.

[joelbernstein]

no longer an issue in the hosted service

Literally still an issue 4 years later. Still no fix?

The tunnel [...] is already bound to another tunnel session

Some other colleague has apparently left ngrok running, on a named tunnel instance. This blocks everybody else. How do we get it back?

[joelbernstein]

I found the UI thing for cancelling a tunnel, but apparently the client is an old version and can't be remotely stopped.

This ngrok agent does not support remote stopping: version 2.1.18 does not support this operation. (ERR_NGROK_805)

Which is, you know, wonderful.