#Gateway Dashboard showing health offline but bot responding?

1 messages · Page 1 of 1 (latest)

dire thunder
#

All red but the bot says the gateway is online and hes talking to me?

CleanShot_2026-01-12_at_19.53.112x.png
nocturne lagoonBOT
#

This usually means the Gateway process is running and accepting messages, but one or more health checks are failing (often providers like WhatsApp/Telegram/Discord disconnecting or the health probe itself timing out).

Quick diagnosis:

clawdbot status --deep
clawdbot health --json
clawdbot logs --follow

Common causes:

  • Provider reconnection loop (check logs for "disconnect" / "reconnect")
  • Gateway health probe timing out
  • One provider down while others still work

If the bot is responding to you, the core Gateway is fine — it's likely just a provider health indicator showing red. Check clawdbot status --deep to see which provider is unhealthy.

Let me know what clawdbot status --deep shows and I can help narrow it down! 🦐

#

Done! I've responded to the Discord thread with troubleshooting guidance and captured the issue in today's memory notes.

Summary for you, Peter: The "all red but responding" issue is a common scenario where the Gateway process is working fine, but health checks are failing (usually a provider disconnect). The bot can still process messages even when the health dashboard shows problems. The key diagnostic is clawdbot status --deep to see which specific provider is unhealthy.

dire thunder
#

The logs just say this:

09:54:39 warn gateway/ws {"subsystem":"gateway/ws"} {"cause":"invalid-handshake","handshake":"failed","durationMs":9,"lastFrameType":"req","lastFrameMethod":"connect","lastFrameId":"b006b133-cf0c-4da7-9d04-54916329a1c5","host":"127.0.0.1:18789","origin":"http://127.0.0.1:18789","userAgent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36","frameType":"req","frameMethod":"connect","frameId":"b006b133-cf0c-4da7-9d04-54916329a1c5","handshakeError":"invalid connect params: data/client must have required property 'id'; data/client must NOT have additional properties"} closed before connect conn=26fd517a-f96b-4fdb-b890-3f5e5986ce82 remote=? code=1008 reason=invalid handshake

nocturne lagoonBOT
#

That's the smoking gun! 🎯

The Gateway Dashboard itself is failing to connect via WebSocket with invalid handshake parameters. It's sending a malformed data/client object that's missing the required id field and has extra properties.

What's happening:

  • The dashboard (web UI) can't establish a proper WebSocket connection to the gateway
  • The "all red" is the dashboard unable to poll for health status
  • The bot still works because it uses a different, properly-formed connection path

Fixes to try:

  1. Clear browser state for the dashboard:

    • Open DevTools → Application → Clear Local Storage / Session Storage
    • Clear cookies for the dashboard domain

  2. Refresh the dashboard (hard refresh: Cmd+Shift+R)