#error: gateway connect failed

1 messages · Page 1 of 1 (latest)

open flint
#

I have the following errors in running: "openclaw logs --follow":

<error>
19:48:24+00:00 warn gateway {"subsystem":"gateway"} security audit: device access upgrade requested reason=scope-upgrade device=15d4db56e02e3274da846ed9bf3963b457a76a6a68b457a0d505f34504424ba4 ip=unknown-ip auth=token roleFrom=operator roleTo=operator scopesFrom=operator.read scopesTo=operator.admin,operator.approvals,operator.pairing,operator.read,operator.talk.secrets,operator.write client=cli conn=971abf95-970f-429e-ac9d-d0f876839995
19:48:24+00:00 error gateway connect failed: GatewayClientRequestError: pairing required
19:48:24+00:00 error gateway connect failed: GatewayClientRequestError: pairing required
19:48:24+00:00 warn gateway/ws {"subsystem":"gateway/ws"} {"cause":"pairing-required","handshake":"failed","durationMs":117,"lastFrameType":"req","lastFrameMethod":"connect","lastFrameId":"9871f7f9-5218-4d0b-84f8-d6ddd1d304d5","host":"127.0.0.1:18789","remoteAddr":"127.0.0.1","remotePort":34260,"localAddr":"127.0.0.1","localPort":18789,"endpoint":"127.0.0.1:34260->127.0.0.1:18789","deviceId":"15d4db56e02e3274da846ed9bf3963b457a76a6a68b457a0d505f34504424ba4","requestId":"d9c1d23a-2c73-4df3-8ad3-d9f16437d07a","reason":"scope-upgrade"} closed before connect conn=971abf95-970f-429e-ac9d-d0f876839995 peer=127.0.0.1:34260->127.0.0.1:18789 remote=127.0.0.1 fwd=n/a origin=n/a host=127.0.0.1:18789 ua=n/a code=1008 reason=pairing required
gateway connect failed: GatewayClientRequestError: pairing required
</error>

opaque prawnBOT
spiral summitBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

opaque prawnBOT
obsidian lilyBOT
#

This looks like a device scope upgrade, not a broken gateway.

Your CLI/device was paired with only operator.read, and now the gateway wants broader scopes, so it is rejecting the connect with pairing required.

Please paste this too, first:

openclaw --version

Then on the gateway host, run:

openclaw devices list
openclaw devices approve <requestId>
#

Then retry:

openclaw logs --follow

Two important gotchas:

  • openclaw devices approve --latest only previews, it does not approve.
  • Re-run openclaw devices list right before approving, because the requestId can change if the device retried.

If devices list also complains, run it locally on the same machine as the gateway, with no explicit --url.

Docs:

#

If it still fails after approval, paste:

openclaw status --all
openclaw devices list --json
open flint
#

this line fix my problem:

openclaw devices list
openclaw devices approve <requestId>

obsidian lilyBOT
#

Nice, glad that fixed it 🎉

Yep, that was a device scope-upgrade / pairing issue. openclaw devices list + openclaw devices approve <requestId> is the right fix.

Docs for future reference: https://docs.openclaw.ai/cli/devices

If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution. That helps Answer Overflow index it for the next person who hits the same error.