#my powershell ans me like this
1 messages ยท Page 1 of 1 (latest)
@raven flint
@raven flint would you please check
The current health check is as follows:
[clawdbot] Failed to start CLI: Error: gateway closed (1006 abnormal closure (no close frame)): no close reason
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: C:\Users\Leran.clawdbot\clawdbot.json
Bind: loopback
at Object.onClose (file:///C:/Users/Leran/AppData/Roaming/npm/node_modules/clawdbot/dist/gateway/call.js:169:22)
at WebSocket.<anonymous> (file:///C:/Users/Leran/AppData/Roaming/npm/node_modules/clawdbot/dist/gateway/client.js:90:32)
at WebSocket.emit (node:events:508:28)
at WebSocket.emitClose (C:\Users\Leran\AppData\Roaming\npm\node_modules\clawdbot\node_modules\ws\lib\websocket.js:263:12)
at emitErrorAndClose (C:\Users\Leran\AppData\Roaming\npm\node_modules\clawdbot\node_modules\ws\lib\websocket.js:1047:13)
at ClientRequest.<anonymous> (C:\Users\Leran\AppData\Roaming\npm\node_modules\clawdbot\node_modules\ws\lib\websocket.js:886:5)
at ClientRequest.emit (node:events:508:28)
at emitErrorEvent (node:_http_client:108:11)
at Socket.socketErrorListener (node:_http_client:575:5)
at Socket.emit (node:events:508:28)
This is a gateway connection issue - the Clawdbot gateway service isn't running or crashed. Here's how to fix it:
Restart the gateway service:
# Stop any existing gateway processes
clawdbot gateway stop
# Or if that fails, manually kill the process:
# Get-Process -Name "clawdbot" | Stop-Process
# Then restart it
clawdbot gateway start
The error 1006 abnormal closure means the WebSocket connection to the gateway (ws://127.0.0.1:18789) was lost - the gateway process probably crashed or wasn't started.
Quick check:
clawdbot gateway status
If it shows "stopped" or fails to connect, just run clawdbot gateway start and you should be back online! ๐ฆ
PS C:\Users\ackc0> git --version
git version 2.52.0.windows.1
PS C:\Users\ackc0> pnpm install -g clawdbot
Packages are hard linked from the content-addressable store to the virtual store.
Content-addressable store is at: C:\Users\ackc0\AppData\Local\pnpm\store\v10
Virtual store is at: .pnpm
โWARNโ 6 deprecated subdependencies found: are-we-there-yet@3.0.1, gauge@4.0.4, node-domexception@1.0.0, npmlog@6.0.2, tar@6.2.1, tar@7.5.4
Packages: +607
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 672, reused 557, downloaded 50, added 607, done
C:\Users\ackc0\AppData\Local\pnpm\global\5:
- clawdbot 2026.1.24-3
โญ Warning โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ โ
โ Ignored build scripts: โ
โ @whiskeysockets/baileys@7.0.0-rc.9, โ
โ clawdbot@2026.1.24-3, node-llama-cpp@3.15.0, โ
โ protobufjs@6.8.8, protobufjs@7.5.4, sharp@0.34.5. โ
โ Run "pnpm approve-builds -g" to pick which dependencies โ
โ should be allowed to run scripts. โ
โ โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
Done in 31.2s using pnpm v10.28.2
PS C:\Users\ackc0>
this is how my powershell ans me
Please paste what PowerShell shows! I need to see the actual output to help you fix it. ๐ฆ
Run this and share the result:
clawdbot gateway status