OCI ARM64: OpenClaw CLI/TUI stuck on WS1008 “pairing required”
Hi, I’m installing OpenClaw 2026.2.19-2 on Oracle Cloud (OCI) and keep hitting a lockout where the gateway runs but CLI/TUI cannot connect. I recreated the VM twice and get the same result.
Env: Ubuntu 24.04.4 LTS (noble) on ARM64/aarch64, kernel 6.17.0-1007-oracle, ~11GiB RAM + 2GiB swap, ~96GB disk. Node v22.22.0, npm 10.9.4, cmake 3.28.3, gcc/g++ 13.3.0. NPM registry reachable.
Install: official installer + QuickStart. Gateway binds to loopback 127.0.0.1:18789 with token auth, installed as systemd user service (lingering enabled).
Problem: service is running/listening, but:
• openclaw gateway status -> WS closed (1008): “pairing required”
• openclaw tui -> “gateway disconnected: pairing required”
Control UI works via SSH tunnel to http://127.0.0.1:18789/ after entering the gateway token; the agent responds in Chat and Instances shows gateway/control-ui connected (control-ui appears as operator). But the server-side CLI/TUI still gets WS1008 “pairing required”.
Tried: Telegram channel configured + sender pairing approved; openclaw gateway install --force + restart; no change. Attempting device/admin actions from CLI (devices list/approve with explicit –url and token) also fails with the same WS1008, so it feels like a catch-22.
Question: what is the correct bootstrap flow to approve the CLI/TUI device in this version, and where in the Control UI are device approvals/pending pairing requests (if not exposed, is there a recommended command/flag)? I can provide redacted logs (requestId/deviceId only).
Env: Ubuntu 24.04.4 LTS (noble) on ARM64/aarch64, kernel 6.17.0-1007-oracle, ~11GiB RAM + 2GiB swap, ~96GB disk. Node v22.22.0, npm 10.9.4, cmake 3.28.3, gcc/g++ 13.3.0. NPM registry reachable.
Install: official installer + QuickStart. Gateway binds to loopback 127.0.0.1:18789 with token auth, installed as systemd user service (lingering enabled).
Problem: service is running/listening, but:
• openclaw gateway status -> WS closed (1008): “pairing required”
• openclaw tui -> “gateway disconnected: pairing required”
Control UI works via SSH tunnel to http://127.0.0.1:18789/ after entering the gateway token; the agent responds in Chat and Instances shows gateway/control-ui connected (control-ui appears as operator). But the server-side CLI/TUI still gets WS1008 “pairing required”.
Tried: Telegram channel configured + sender pairing approved; openclaw gateway install --force + restart; no change. Attempting device/admin actions from CLI (devices list/approve with explicit –url and token) also fails with the same WS1008, so it feels like a catch-22.
Question: what is the correct bootstrap flow to approve the CLI/TUI device in this version, and where in the Control UI are device approvals/pending pairing requests (if not exposed, is there a recommended command/flag)? I can provide redacted logs (requestId/deviceId only).
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Similar Threads
Was this page helpful?
