// ERR_NGROK_6024
ngrok ERR_NGROK_6024 — auth token revoked: how to recover
ERR_NGROK_6024 means the token presented by the agent has been revoked. The agent will keep failing until you replace it.
What it means
Tokens are revoked manually (you clicked Revoke in the dashboard), automatically (your account changed plan), or as part of a security incident response. The signature is rejected at the edge.
Common causes
- You revoked the token deliberately and forgot the agent was still using it.
- An admin on a shared account rotated tokens.
- Plan downgrade invalidated paid-plan tokens.
How to fix it on ngrok
1. Issue a fresh token in the dashboard
2. Update the agent
$ ngrok config add-authtoken <new-token>
// the same workflow on lrok
lrok shows token state on /dashboard/tokens — name, last-used timestamp, and revoke action. When a CLI session uses a revoked token, the agent prints 'token revoked, run lrok login' instead of an opaque error code.
1. See your tokens
lrok.io/dashboard/tokens lists all active and revoked tokens.
2. Re-authenticate
$ lrok login # opens browser; emits a fresh token