Issues running gateway in docker on google cloud
✅Solved
I'm trying to run the gateway in docker on google cloud vm, i've ran the docker-setup.sh. Then I made an ssh tunnel from my local machine to the VM, i can access the ui in my browser but i see 'disconnected (1008): pairing required'.
I've tried the suggested steps in the docs for this issue but
docker compose run --rm openclaw-cli devices list
fails with
[openclaw] CLI failed: Error: gateway closed (1006 abnormal closure (no close frame)): no close reason
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: /home/node/.openclaw/openclaw.json
Bind: loopback
at Object.onClose (file:///app/dist/call-D9ZE2Tl4.js:262:10)
at WebSocket.<anonymous> (file:///app/dist/client-DQ_l_0dt.js:1420:23)
at WebSocket.emit (node:events:519:28)
at WebSocket.emitClose (/app/node_modules/.pnpm/ws@8.19.0/node_modules/ws/lib/websocket.js:263:12)
at emitErrorAndClose (/app/node_modules/.pnpm/ws@8.19.0/node_modules/ws/lib/websocket.js:1047:13)
at ClientRequest.<anonymous> (/app/node_modules/.pnpm/ws@8.19.0/node_modules/ws/lib/websocket.js:886:5)
at ClientRequest.emit (node:events:519:28)
at emitErrorEvent (node:_http_client:107:11)
at Socket.socketErrorListener (node:_http_client:574:5)
at Socket.emit (node:events:519:28)
I've tried the suggested steps in the docs for this issue but
docker compose run --rm openclaw-cli devices list
fails with
[openclaw] CLI failed: Error: gateway closed (1006 abnormal closure (no close frame)): no close reason
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: /home/node/.openclaw/openclaw.json
Bind: loopback
at Object.onClose (file:///app/dist/call-D9ZE2Tl4.js:262:10)
at WebSocket.<anonymous> (file:///app/dist/client-DQ_l_0dt.js:1420:23)
at WebSocket.emit (node:events:519:28)
at WebSocket.emitClose (/app/node_modules/.pnpm/ws@8.19.0/node_modules/ws/lib/websocket.js:263:12)
at emitErrorAndClose (/app/node_modules/.pnpm/ws@8.19.0/node_modules/ws/lib/websocket.js:1047:13)
at ClientRequest.<anonymous> (/app/node_modules/.pnpm/ws@8.19.0/node_modules/ws/lib/websocket.js:886:5)
at ClientRequest.emit (node:events:519:28)
at emitErrorEvent (node:_http_client:107:11)
at Socket.socketErrorListener (node:_http_client:574:5)
at Socket.emit (node:events:519:28)
Solution
Nice — yep, quoting bites people a lot (esp. if the token has characters your shell/compose env expansion messes with).
If this fixed it, next steps are:
1) Approve the browser device:
2) Reload the Control UI tab — it should flip from “pairing required” to connected.
Glad that helped! If you’re all set now, please right-click the solution message → Apps →
Mark Solution so Answer Overflow indexes it for the next person.
If this fixed it, next steps are:
1) Approve the browser device:
2) Reload the Control UI tab — it should flip from “pairing required” to connected.
Glad that helped! If you’re all set now, please right-click the solution message → Apps →
Mark Solution so Answer Overflow indexes it for the next person.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Was this page helpful?
