ERR_NGROK_702: Too many connections! The tunnel session SESSION has violated the rate-limit policy of THRESHOLD connections per minute by initiating COUNT connections in the last SECONDS seconds

​

What does ERR_NGROK_702 mean?

Too many connections! The tunnel session <SESSION> has violated the rate-limit policy of <THRESHOLD> connections per minute by initiating <COUNT> connections in the last <SECONDS> seconds. Decrease your inbound connection volume or upgrade to a paid plan for additional capacity.

​

Why does ngrok return ERR_NGROK_702?

• ngrok limits the number of inbound connections to your tunnels.
• Limits are imposed on connections, not requests. If your HTTP clients use persistent connections, also known as HTTP keep-alive (most modern ones do), you’ll likely never hit this limit.
• ngrok will return a 429 response to HTTP connections that exceed the rate limit.
• Connections to TCP and TLS tunnels violating the rate limit will be closed without a response.

​

How do I fix ERR_NGROK_702?

• Upgrade your account to a Pro or Pay-as-you-go plan from your account dashboard to reserve a custom hostname.

​

Where can I get more help with ERR_NGROK_702?