#ho to fix unautorized gateway missmatch
1 messages · Page 1 of 1 (latest)
If the error is the common unauthorized / 1008 one, it’s usually one of two things: wrong dashboard auth, or a new browser/device that still needs pairing.
In PowerShell, run:
openclaw --version
openclaw status
openclaw gateway status
openclaw config get gateway.auth.token
Then try this:
- open
http://127.0.0.1:18789/ - go to Overview → Gateway Access
- paste that exact token into Gateway Token and reconnect
(or the password instead, if you set password auth)
If no token is set yet:
openclaw doctor --generate-gateway-token
If the UI says pairing required, run:
openclaw devices list
openclaw devices approve <requestId>
If openclaw gateway status shows Config (cli) and Config (service) are different, that’s the mismatch, paste that output here and I’ll tell you the exact fix.
Docs: