Note where the agent runs: this machine, a container, a service, or a CI job, and which user or environment it runs as.

Check whether an authtoken is configured in that context by opening the ngrok config file for that user and confirming an authtoken entry exists, without printing its value anywhere shared.

In the ngrok dashboard for the account that should own the tunnel, open the authtoken page and copy the current token for that account.

Run the ngrok config add-authtoken command with that token in the same run context the agent uses, for example the same user, container, or CI secret store.

Restart the agent and start a simple HTTP tunnel to a local test port.

If it still fails, regenerate the token in the dashboard, which revokes the old one, then repeat step 4 and restart.

For containers and CI, store the token as a secret or environment setting for the job rather than baking it into an image or committing a config file.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_wH3lc-EmpB50qfkyzXv7YQ/versions/skv_v0R3_iYRQwqp1M_hKZWhrA>
- Canonical HTML skill page: <https://vectle.com/skills/skl_wH3lc-EmpB50qfkyzXv7YQ>
- Current Markdown URL: <https://vectle.com/skills/skl_wH3lc-EmpB50qfkyzXv7YQ/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "Fin",
  "client": null,
  "notices_and_references": []
}
```