openclaw - 💡(How to fix) Fix [Bug]: Windows gateway listens but local health/status time out after Telegram polling stall (v2026.5.20) [1 pull requests]

%APPDATA%\npm\openclaw.cmd gateway install --force --port 18789

---

%APPDATA%\npm\openclaw.cmd gateway restart

---

%APPDATA%\npm\openclaw.cmd gateway status

---

Invoke-WebRequest -UseBasicParsing http://127.0.0.1:18789/health -TimeoutSec 8

---

Runtime: running (pid 2772, Startup-folder login item installed; listener detected on port 18789.)
Listening: 127.0.0.1:18789
Connectivity probe: failed
Probe target: ws://127.0.0.1:18789
  timeout
Port 18789 is already in use.
- pid 2772: "C:\Program Files\nodejs\node.exe" ... openclaw\dist\index.js gateway --port 18789 (127.0.0.1:18789)

---

HEALTH_ERR The operation has timed out.

---

LocalAddress  : 127.0.0.1
LocalPort     : 18789
State         : Listen
OwningProcess : 2772

---

http server listening (10 plugins: browser, canvas, codex, device-pair, duckduckgo, file-transfer, memory-core, phone-control, talk-voice, telegram; 14.8s)
gateway ready
heartbeat: started
[default] starting provider (@...bot)

---

liveness warning: reasons=event_loop_delay,event_loop_utilization,cpu interval=157s eventLoopDelayP99Ms=136902.1 eventLoopDelayMaxMs=136902.1 eventLoopUtilization=0.999 cpuCoreRatio=1.019 active=1 waiting=0 queued=0 ... work=[active=agent:main:telegram:direct:<redacted>(processing,q=1,age=140s)]
stuck session: sessionId=unknown sessionKey=agent:main:telegram:direct:<redacted> state=processing age=140s queueDepth=1 reason=queued_work_without_active_run classification=stale_session_state recovery=checking
stuck session recovery: sessionId=unknown sessionKey=agent:main:telegram:direct:<redacted> age=140s action=release_lane aborted=false drained=true released=0
stuck session recovery outcome: status=released action=release_lane sessionId=unknown sessionKey=agent:main:telegram:direct:<redacted> lane=session:agent:main:telegram:direct:<redacted> released=0
[telegram] Polling stall detected (active getUpdates stuck for 139.83s); forcing restart. [diag inFlight=1 outcome=started startedAt=<redacted> finishedAt=n/a durationMs=n/a offset=<redacted>]
[telegram][diag] isolated polling ingress finished reason=polling stall detected inFlight=1 outcome=started startedAt=<redacted> finishedAt=<redacted> durationMs=30176 offset=<redacted>
[telegram][diag] closing stale transport before rebuild
[telegram][diag] rebuilding transport for next polling cycle
closed before connect conn=<redacted> peer=127.0.0.1:<port>->127.0.0.1:18789 remote=127.0.0.1 host=127.0.0.1:18789 code=1006 reason=n/a

---

telegram setMyCommands(all_group_chats) failed: Network request for 'setMyCommands' failed!
Telegram command sync failed: HttpError: Network request for 'setMyCommands' failed!
fetch fallback: DNS-resolved IP unreachable; trying alternative Telegram API IP (codes=none, reason=request-timeout)
telegram deleteMyCommands(all_group_chats) failed: Network request for 'deleteMyCommands' failed!
telegram sendChatAction failed: Network request for 'sendChatAction' failed!

---

Delivery suppressed by sourceReplyDeliveryMode: message_tool_only for session agent:main:telegram:direct:<redacted> — agent will still process the message

---

{
  "messages": {
    "visibleReplies": "automatic"
  }
}