// ERR_NGROK_108
ngrok ERR_NGROK_108 — too many tunnels: causes and fix
ERR_NGROK_108 fires when your ngrok account already has the maximum number of simultaneous tunnels open and a new ngrok start would push past the limit.
What it means
The error refuses a new tunnel because your account is already running the per-plan limit (1 tunnel on the free plan, more on paid). It is not a transient failure — restarting won't help; you have to free a slot or upgrade.
Common causes
- A previous ngrok process didn't shut down cleanly and is still holding the slot.
- You have ngrok running on another machine signed in to the same account.
- You hit the plan limit (free = 1, paid plans vary).
How to fix it on ngrok
1. List active tunnels and pick the stale one
curl -s -H "Authorization: Bearer $NGROK_API_KEY" https://api.ngrok.com/tunnels | jq2. Stop the orphaned tunnel
Use the API DELETE /tunnels/{id} or kill the local ngrok process holding it.
3. Upgrade if you genuinely need more
ngrok Pro raises the simultaneous tunnel cap.
// the same workflow on lrok
lrok's free plan also caps active tunnels at 1, but the cap is enforced per-process: if your terminal session ends, the tunnel ends. There's no orphan-process state to chase. Pro is $9/mo flat for unlimited tunnels — no per-tunnel pricing.
1. Install
$ curl -fsSL https://lrok.io/install.sh | sh2. Sign in (browser-based, no copy-paste)
$ lrok login3. Start a tunnel
$ lrok http 3000