// ERR_NGROK_3200
ngrok ERR_NGROK_3200 — tunnel endpoint offline: how to fix
ERR_NGROK_3200 means a request reached ngrok's edge but the local agent hasn't dialed in yet — the public URL is alive but the tunnel behind it is missing.
What it means
ngrok received an HTTP request for your subdomain but the agent (the ngrok process on your laptop) is not connected. The visitor sees a tunnel-offline error page; ngrok returned 502/504 to them.
Common causes
- Your laptop went to sleep and the ngrok process is suspended.
- Wi-Fi flaked and the agent's TLS connection dropped without reconnecting.
- The local server you were tunneling crashed and the agent exited along with it.
How to fix it on ngrok
1. Restart the agent
$ ngrok http 3000 # or your usual command2. Run with --log to see why the agent dropped
$ ngrok http 3000 --log=stdout3. For long-running dev sessions, disable laptop sleep
On macOS: caffeinate -i ngrok http 3000 keeps the system awake while the tunnel runs.
// the same workflow on lrok
lrok prints the actual error message at the agent (e.g. 'connection lost — reconnecting...') instead of returning a generic 502 from the edge. Inspector requests captured before the disconnect remain in /dashboard so you can replay them once the tunnel is back.
1. Start tunnel
$ lrok http 30002. Reconnects automatically
Network blips reconnect within seconds; the agent prints status to stderr so you see what happened.
3. Captured requests survive the blip
The last 100 requests stay in the inspector at https://lrok.io/dashboard/tunnels/<sub> — replay any of them once you are back online.