Can't access to dashboard

[feral solstice]

RPC probe: failed
RPC target: ws://127.0.0.1:18789
gateway closed (1006 abnormal closure (no close frame)): no close reason
Gateway target: ws://127.0.0.1:18789
Source: cli --url
Config: C:\Users\Дом.openclaw\openclaw.json
this is only error I get
Windows 11

[ebon tendon]

This error (1006 abnormal closure) means the WebSocket connection to the Gateway was lost before completing. Here's how to troubleshoot:

Quick Checks

1. Is Gateway running?

   clawdbot gateway status
   

   If not running: clawdbot gateway start

2. Port in use?
   Check if port 18789 is actually open:

   netstat -an | findstr 18789
   

   On Windows PowerShell: Get-NetTCPConnection -LocalPort 18789

3. Check your config
   The path shows C:\Users\Дом\.openclaw\openclaw.json — the username has Cyrillic characters, which can sometimes cause path issues. Try:

   • Moving config to a path without special characters
   • Running terminal as Administrator

4. Firewall/Antivirus
   Temporarily disable Windows Defender Firewall or other AV to test if it's blocking localhost connections.

Common Fixes

• Run terminal as Administrator (right-click → Run as administrator)
• Check if Gateway already running on another port
• Delete lock file: rm ~/.moltbot/gateway.lock (if exists)
• Reinstall: pnpm moltbot gateway stop then start again

Can you confirm whether the Gateway is currently running? (clawdbot gateway status)

[feral solstice]

🦞 OpenClaw 2026.1.29 (a5b4d22) — Your AI assistant, now without the $3,499 headset.

│
◇
Service: Scheduled Task (registered)
File logs: \tmp\openclaw\openclaw-2026-01-30.log
Command: C:Program Filesnodejsnode.exe C:UsersДомAppDataRoamingnpmnode_modulesopenclawdistindex.js gateway --port 18789
Service env: OPENCLAW_GATEWAY_PORT=18789

Config (cli): C:\Users\Дом.openclaw\openclaw.json
Config (service): C:\Users\Дом.openclaw\openclaw.json

Gateway: bind=loopback (127.0.0.1), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.

Runtime: unknown
RPC probe: failed
RPC target: ws://127.0.0.1:18789
gateway closed (1006 abnormal closure (no close frame)): no close reason
Gateway target: ws://127.0.0.1:18789
Source: cli --url
Config: C:\Users\Дом.openclaw\openclaw.json

it said that localport 18789 wasn't found

[feral solstice]

through Get-NetTCPConnection -LocalPort 18789

[feral solstice]

@ebon tendon what should I do

[ebon tendon]

Let's diagnose this! Run these commands in PowerShell (as Administrator):

1. Check if gateway is running:

clawdbot gateway status

2. If not running, start it:

clawdbot gateway start

3. If that fails, try a full restart:

clawdbot gateway stop
clawdbot gateway start

Report back what you see — especially any error messages. 🦐

[ebon tendon]

Sent you the diagnostic steps! Run those commands and share the output — that will help pinpoint exactly what's going wrong with the Gateway connection.

[feral solstice]

ok, got it, 2 minutes

[ebon tendon]

Sounds good! Take your time — I'll be here when you're ready with the results. 🦐

[feral solstice]

🦞 OpenClaw 2026.1.29 (a5b4d22) — If you're lost, run doctor; if you're brave, run prod; if you're wise, run tests.

│
◇
Service: Scheduled Task (registered)
File logs: \tmp\openclaw\openclaw-2026-01-30.log
Command: C:Program Filesnodejsnode.exe C:UsersДомAppDataRoamingnpmnode_modulesopenclawdistindex.js gateway --port 18789
Service env: OPENCLAW_GATEWAY_PORT=18789

Config (cli): C:\Users\Дом.openclaw\openclaw.json
Config (service): C:\Users\Дом.openclaw\openclaw.json

Gateway: bind=loopback (127.0.0.1), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.

Runtime: unknown
RPC probe: failed
RPC target: ws://127.0.0.1:18789
gateway closed (1006 abnormal closure (no close frame)): no close reason
Gateway target: ws://127.0.0.1:18789
Source: cli --url
Config: C:\Users\Дом.openclaw\openclaw.json

2
🦞 OpenClaw 2026.1.29 (a5b4d22) — I'm basically a Swiss Army knife, but with more opinions and fewer sharp edges.

Restarted Scheduled Task: OpenClaw Gateway

is that good or I need full restart too?

as I said this was the only error message

Runtime: unknown
RPC probe: failed
RPC target: ws://127.0.0.1:18789
gateway closed (1006 abnormal closure (no close frame)): no close reason
Gateway target: ws://127.0.0.1:18789
Source: cli --url
Config: C:\UsersДом.openclaw\openclaw.json

from status

[ebon tendon]

I can see the service is registered but the probe is failing. The gateway process might be crashing shortly after startup. Let's check the logs:

Check the logs:

cat \tmp\openclaw\openclaw-2026-01-30.log

Or on PowerShell:

Get-Content \tmp\openclaw\openclaw-2026-01-30.log -Tail 50

Try a full restart:

clawdbot gateway stop
# Wait 5 seconds

[ebon tendon]

clawdbot gateway start
clawdbot gateway status

The Cyrillic username (Дом) in the path could also be causing issues. Does your user folder path have special characters?

Can you share the last 30-50 lines of the log file? That's where we'll see what's actually crashing the gateway.

[ebon tendon]

Good, it's restarting! But we still need to see the logs to find the actual error. The gateway might be crashing right after startup.

Run this to see the error:

Get-Content \tmp\openclaw\openclaw-2026-01-30.log -Tail 30

Or if that doesn't work:

clawdbot doctor

The log file will show us exactly what's causing the 1006 crash. Share what you see! 🦐