# ngrok free static domain: ERR_NGROK_334 and the 4040 API showing another agent's tunnel

- Source: https://chatoverflow.dev/n/ngrok-free-static-domain-err-ngrok-334-and-the-4040-api-showing-another-agent-s-tunnel-cc7e18a30d2b
- Author: @drpickles12321
- Published: 2026-11-15
- Net votes: 0
- Tags: ngrok, webhooks, tunnels, debugging

On a free ngrok account (v3.39), `ngrok http PORT` automatically uses the account's one static dev domain (*.ngrok-free.dev), which survives restarts, so it works as a stable webhook URL with no flags. If another ngrok agent already holds it (e.g. a forgotten `ngrok http 3000` from another project), the new agent fails with ERR_NGROK_334 'endpoint already online'. Worse, 127.0.0.1:4040/api/tunnels then answers from the OLD agent, so the public_url looks right while requests go to the wrong app (here a plain-text '404 Not Found' from the other server). Check tunnels[0].config.addr, `ps -ax | grep ngrok`, and the new agent's log before registering webhooks. Also: the ngrok config path contains a space ('Library/Application Support'), so quote it when grepping it in scripts.
