Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Telegram group reply not working + connectivity probe timeout on ws://127.0.0.1 [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#74918•Fetched 2026-05-01 05:39:56
View on GitHub
Comments
2
Participants
2
Timeline
4
Reactions
2
Author
nakedsleepwalkernakedsleepwalker
Participants
clawsweeper[bot]clawsweeper[bot]nakedsleepwalkernakedsleepwalker
Timeline (top)
commented ×2closed ×1subscribed ×1

Two symptoms that appear to be related:

Root Cause

Suspected root cause

The WebSocket loopback probe (ws://127.0.0.1:XXXXX) times out, suggesting the gateway internal RPC/WebSocket server is unresponsive or partially hung. The Telegram outbound path likely relies on this internal WS → group replies fail because the outbound dispatch channel is dead.

Fix Action

Fix / Workaround

Suspected root cause

The WebSocket loopback probe (ws://127.0.0.1:XXXXX) times out, suggesting the gateway internal RPC/WebSocket server is unresponsive or partially hung. The Telegram outbound path likely relies on this internal WS → group replies fail because the outbound dispatch channel is dead.

RAW_BUFFERClick to expand / collapse

Description

Two symptoms that appear to be related:

1. Telegram group replies not working

  • Private chat replies in Telegram work fine.
  • Group chat replies silently fail — messages are received (logged in commands.log) but no response is sent back to the group.
  • Config shows groupPolicy: "open" and requireMention: false for affected groups.

2. Connectivity probe: failed (timeout)

  • openclaw gateway status shows:
    • Runtime: running (pid active)
    • Connectivity probe: failed
    • Probe target: ws://127.0.0.1:XXXXX → timeout
  • Gateway API calls also time out (e.g. config.schema.lookup fails after 30s).
  • The gateway process runs under systemd user service (openclaw-gateway.service) with Node v22.22.0 via nvm.
  • systemctl --user restart openclaw-gateway aborts with SIGTERM; only pkill -9 -f openclaw can kill the process.

Environment

  • openclaw v2026.4.27
  • Node v22.22.0 (via nvm)
  • OS: Linux (OpenCloudOS)
  • Run mode: systemd user service
  • Telegram channel enabled, polling mode

Suspected root cause

The WebSocket loopback probe (ws://127.0.0.1:XXXXX) times out, suggesting the gateway internal RPC/WebSocket server is unresponsive or partially hung. The Telegram outbound path likely relies on this internal WS → group replies fail because the outbound dispatch channel is dead.

Steps to reproduce

  1. Start gateway via systemd user service
  2. openclaw gateway status shows probe failure
  3. Send message to any configured Telegram group → message appears in commands.log but no reply sent
  4. Attempt systemctl --user restart openclaw-gateway → command hangs/aborts

Expected behavior

  • Connectivity probe should succeed
  • Telegram group replies should work
  • Gateway restart should complete cleanly

extent analysis

TL;DR

The issue can be mitigated by investigating and resolving the WebSocket loopback probe timeout, which is likely causing the Telegram group replies to fail.

Guidance

  • Investigate the WebSocket server configuration and implementation to ensure it is properly handling connections and responding to probes.
  • Verify the openclaw-gateway service is properly configured to run under systemd, and check for any resource limitations or conflicts that may be causing the process to hang or timeout.
  • Check the Node.js version and dependencies to ensure they are compatible with the openclaw version and the WebSocket library being used.
  • Attempt to manually kill and restart the openclaw-gateway process using pkill -9 -f openclaw and then restart the service to see if it resolves the issue temporarily.

Example

No code snippet is provided as the issue is more related to configuration and process management.

Notes

The root cause of the issue is likely related to the WebSocket loopback probe timeout, but further investigation is needed to determine the exact cause. The fact that the process can only be killed using pkill -9 -f openclaw suggests a potential issue with the process management or resource handling.

Recommendation

Apply workaround: manually kill and restart the openclaw-gateway process using pkill -9 -f openclaw and then restart the service, as this may temporarily resolve the issue and allow for further debugging.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

  • Connectivity probe should succeed
  • Telegram group replies should work
  • Gateway restart should complete cleanly
#api#ssr#installation#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING