Fix: Gateway Token Missing

What It Means

Your WebChat or dashboard can't connect to the OpenClaw gateway because it's not passing the authentication token correctly. Think of it like showing up to a building with an ID badge that doesn't match the security system — you're not getting in.

Common Causes

• •You set up gateway.auth.token but forgot to add gateway.remote.token
• •The tokens don't match exactly (even a single character difference will fail)
• •You changed your auth token but didn't update the remote token
• •Using WebChat without passing the token in the URL

Ask Your Agent to Fix This

Copy this prompt and send it to your OpenClaw agent. It will check your config and fix the token mismatch:

Fix It Manually

{
  "gateway": {
    "remote": {
      "token": "YOUR_AUTH_TOKEN"
    },
    "auth": {
      "token": "YOUR_AUTH_TOKEN"
    }
  }
}

Verify the Fix

After fixing, check your gateway status:

Or try connecting to WebChat again. If using the URL method, make sure to include the token:

How to Prevent This

• ✓Set both tokens at the same time when configuring
• ✓Run openclaw security audit after any config changes
• ✓Use the CLI (openclaw chat) instead of WebChat to avoid token URL issues

Related Errors

Related Guides