// ERR_NGROK_6022
ngrok ERR_NGROK_6022 — auth failed: causes and fix
ERR_NGROK_6022 means the auth token your agent presented was rejected by the ngrok control plane.
What it means
Your ngrok auth token is missing, mistyped, or revoked. Until it's fixed, the agent can't open a tunnel.
Common causes
- ngrok config edit pasted the token incorrectly (extra newline, missing character).
- You revoked the token in the ngrok dashboard.
- You're signed into a different ngrok account than the one the token came from.
How to fix it on ngrok
1. Print your saved token
$ ngrok config check2. Reset it from the dashboard
ngrok dashboard → Auth → Your Authtoken. Copy and paste exactly.
3. Re-add it via the CLI
$ ngrok config add-authtoken <your-token>
// the same workflow on lrok
lrok login uses a browser-based handshake instead of a copy-paste token — you click 'Authorize' in the browser, the CLI receives the token over a one-shot callback. No mistyped tokens, no per-machine config files to keep in sync.
1. Sign in
$ lrok login2. No browser? Issue an API token from the dashboard
lrok.io/dashboard/tokens → Create token. Then run: lrok login --no-browser and paste.