// ERR_NGROK_708
ngrok ERR_NGROK_708 — too many connections: how to fix
ERR_NGROK_708 throttles you when too many concurrent connections hit a single tunnel.
What it means
ngrok rate-limits connections per tunnel (and per plan). Crossing the cap returns 708 to subsequent connections; existing ones keep flowing.
Common causes
- Load test with too many parallel clients.
- Mobile app reconnect storm after a network blip.
- WebSocket clients reconnecting in a tight loop.
How to fix it on ngrok
1. Stagger reconnect attempts in the client
Exponential backoff with jitter, 1s → 30s.
2. Upgrade your ngrok plan if the load is genuine.
// the same workflow on lrok
lrok doesn't impose a connections-per-tunnel cap on the free or Pro plans. The bottleneck moves back to where it should be — your local server.
1. Standard tunnel
$ lrok http 30002. Or TCP for non-HTTP load
$ lrok tcp 5432