#Gateway connect failed

1 messages · Page 1 of 1 (latest)

heavy copper
#

Gateway connect failed: error: pairing required
Gateway not reachable

I can’t figure out how to move past this error.

heavy copper
#

Nevermind. I confirmed the gateway is actually good. It’s an invalid bearer token error.

stray gazelleBOT
#

Yep — “invalid bearer token” almost always just means the Control UI/CLI is sending a stale/wrong Gateway token (the Gateway is up, auth is failing).

Things to check / quickest fixes:

  1. Confirm what auth mode the Gateway expects
openclaw config get gateway.auth.mode
openclaw config get gateway.auth.token
  1. Make the Control UI use the same token
  • In the dashboard, go to Control → Overview → Gateway Access
  • Paste the value of gateway.auth.token into the Gateway Token field (not the Password field), then Connect.
  1. Clear the UI’s cached token
    The dashboard stores the token in browser localStorage, so if you rotated it you’ll keep getting “invalid bearer token” until you clear it.
  • Easiest: open the dashboard in an incognito/private window, paste token again.