Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix v2026.4.24+ gateway probe timeout / channels never connect on Linux [2 comments, 3 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#74568•Fetched 2026-04-30 06:23:00
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
2
Author
Alpy87Alpy87
Participants
Alpy87Alpy87clawsweeper[bot]clawsweeper[bot]steipetesteipete
Timeline (top)
commented ×2closed ×1cross-referenced ×1mentioned ×1

After updating to 2026.4.24 (or 2026.4.26), the gateway binary updates to the new version and appears to start (HTTP server listening, "ready" logged), but the connectivity probe times out at 10s and no channels connect. Rollback to 2026.4.22 restores full function.

Root Cause

After updating to 2026.4.24 (or 2026.4.26), the gateway binary updates to the new version and appears to start (HTTP server listening, "ready" logged), but the connectivity probe times out at 10s and no channels connect. Rollback to 2026.4.22 restores full function.

Fix Action

Workaround

Stay on 2026.4.22.

RAW_BUFFERClick to expand / collapse

Summary

After updating to 2026.4.24 (or 2026.4.26), the gateway binary updates to the new version and appears to start (HTTP server listening, "ready" logged), but the connectivity probe times out at 10s and no channels connect. Rollback to 2026.4.22 restores full function.

Environment

  • OS: Linux (Ubuntu 24.04)
  • Install method: npm global (npm install -g openclaw)
  • Gateway service: systemd user service
  • Channels: telegram, whatsapp, discord
  • GPU: RTX 2080 (Ollama for local embeddings)

Symptoms

  • openclaw gateway status shows Runtime: running but Connectivity probe: failed (timeout)
  • No channels connect (Telegram/WhatsApp stay offline)
  • Gateway log shows "ready (9 plugins)" but channels never initialize
  • Rollback to 4.22 via npm install -g [email protected] + systemctl --user restart openclaw-gateway.service restores everything
  • Same behavior on both 4.24 and 4.26

Reproduction

  1. npm install -g [email protected]
  2. systemctl --user restart openclaw-gateway.service
  3. openclaw gateway status → probe timeout, channels never connect

Suspected cause

The Pi package bump (@mariozechner/pi-agent-core 0.69.0 → 0.70.2, along with pi-ai, pi-tui, pi-coding-agent) may cause the agent runner initialization to hang or fail during gateway startup, blocking channel initialization even though the HTTP listener starts successfully.

Workaround

Stay on 2026.4.22.

Related

  • #72526 describes similar post-upgrade gateway instability (on macOS with bonjour)
  • The DeepSeek thinking/replay fix in 4.24 is needed, but 4.24+ is currently unusable on this Linux setup

extent analysis

TL;DR

Downgrade to version 2026.4.22 to restore gateway functionality until the issue with the Pi package bump is resolved.

Guidance

  • Verify that the issue is indeed caused by the Pi package bump by checking the gateway logs for any errors related to the agent runner initialization.
  • Try to isolate the specific package causing the issue by checking the dependencies of @mariozechner/pi-agent-core and testing different versions.
  • Consider testing the gateway with a minimal configuration to see if the issue persists, which could help identify if the problem is specific to certain channels or plugins.
  • Monitor the related issue #72526 for any updates or fixes that may apply to this situation.

Example

No code snippet is provided as the issue seems to be related to a package version conflict rather than a code-specific problem.

Notes

The provided workaround of staying on version 2026.4.22 is a temporary solution. It's essential to continue monitoring for updates or fixes related to the Pi package bump to ensure the gateway remains stable and secure.

Recommendation

Apply the workaround by downgrading to version 2026.4.22, as it is the only known stable version that restores full functionality, despite missing the DeepSeek thinking/replay fix in 4.24.

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…
#response parsing#generation error#database connection#vector store#embedding generation

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix v2026.4.24+ gateway probe timeout / channels never connect on Linux [2 comments, 3 participants]