openclaw - ✅(Solved) Fix [Bug]: Gateway crashes after update to 2026.4.24 (CIAO PROBING CANCELLED) [1 pull requests, 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#72339Fetched 2026-04-27 05:31:22
View on GitHub
Comments
2
Participants
3
Timeline
9
Reactions
1
Author
Timeline (top)
referenced ×4commented ×2closed ×1cross-referenced ×1

📋 Description

After updating OpenClaw from 2026.4.23 to 2026.4.24, the gateway no longer stays running. It appears to start successfully, but then crashes due to a Bonjour/ciao probing issue.

Root Cause

📋 Description

After updating OpenClaw from 2026.4.23 to 2026.4.24, the gateway no longer stays running. It appears to start successfully, but then crashes due to a Bonjour/ciao probing issue.

Fix Action

Fixed

PR fix notes

PR #72332: fix(gateway): suppress Windows console flicker and prevent Bonjour fatal crashes (#70238, #72344, #72339)

Description (problem / solution / changelog)

fix(gateway): suppress Windows console flicker and prevent Bonjour fatal crashes (#70238, #72344, #72339)

Summary

  • Problem: On Windows, launching the gateway causes jarring command prompt flickers. More critically, on both Linux and Windows, the Bonjour plugin causes fatal gateway crashes due to unhandled CIAO PROBING CANCELLED rejections and hard process.exit(1) calls in the @homebridge/ciao dependency when mDNS conflicts (like Avahi) occur.
  • Why it matters: This range of issues makes the gateway appear unstable on Windows and entirely unusable on many headless Linux VPS environments where mDNS stacks often conflict.
  • What changed: - Windows Flicker Fix: Added windowsHide: true to the TUI spawn and patched 6 exec calls within @homebridge/ciao.
    • Plugin Shielding: Updated advertiser.ts with error helpers to catch and suppress CANCELLED errors, logging them as debug instead of allowing them to crash the process.
    • Dependency Hardening: Patched @homebridge/[email protected] to replace process.exit(1) with console.warn() in CiaoService.js and Responder.js recovery paths.
    • Conflict Resilience: Added detection for EADDRINUSE. If a conflict (e.g., Avahi) is detected, the plugin now logs a warning and disables itself gracefully rather than crashing the core service.
  • What did NOT change: No changes were made to core networking logic or discovery protocols.

Change Type

  • Bug fix
  • Security hardening (Stability)
  • Refactor required for the fix (Dependency patch)

Scope

  • Gateway / orchestration
  • Integrations (Bonjour/mDNS)
  • UI / DX

Linked Issues

  • Closes #70238
  • Closes #72344
  • Closes #72339
  • This PR fixes a bug or regression

Root Cause

  1. Visual Flicker: Missing windowsHide flags on child process spawns in both internal code and dependencies.
  2. Fatal Crashes: Probing cancellations from ciao were leaking as unhandled promise rejections during watchdog restarts.
  3. Hard Exits: The @homebridge/ciao library utilized process.exit(1) for internal network interface update failures, which is inappropriate for a plugin-level dependency.

User-visible / Behavior Changes

  • Windows: Silent startup without flashing cmd.exe windows.
  • Linux: Resilience against existing Avahi/mDNS stacks; the gateway logs a conflict warning and continues to run.
  • General: Improved reliability; Bonjour failures are no longer fatal to the core gateway process.

Repro + Verification

Environment

  • OS: Windows 11 / Ubuntu 24.04 (Headless VPS)
  • Runtime: Node v22+
  • Tooling: pnpm

Steps

  1. Start gateway on Windows -> Verified: No visible console flickers.
  2. Start gateway on Linux with avahi-daemon active -> Verified: Logs mDNS conflict detected, gateway remains stable.
  3. Trigger watchdog re-advertise cycle -> Verified: CANCELLED errors caught, process stays alive.

Evidence

  • All 29 bonjour extension tests pass.
  • Verified pnpm patch-commit for @homebridge/[email protected] contains both visibility flags and exit-trap removals.
  • Confidence Score: 5/5 (Greptile)

Human Verification

  • Verified scenarios: Local Windows 11 build; Headless Linux VPS (Contabo) with Avahi conflict.
  • Edge cases checked: Relaunching the gateway multiple times; manual watchdog triggers.

Changed files

  • extensions/bonjour/src/advertiser.test.ts (modified, +32/-0)
  • extensions/bonjour/src/advertiser.ts (modified, +86/-20)
  • package.json (modified, +2/-1)
  • patches/@[email protected] (added, +94/-0)
  • pnpm-lock.yaml (modified, +5/-2)
  • src/plugins/jiti-loader-cache.test.ts (modified, +1/-5)
  • src/tui/tui-launch.ts (modified, +1/-0)

Code Example

📄 Logs
<details> <summary>Click to expand logs</summary>
12:04:37 [gateway] ready (6 plugins: acpx, bonjour, browser, device-pair, phone-control, talk-voice; 94.4s)
12:04:37 [gateway] starting channels and sidecars...

12:07:12 [plugins] bonjour: watchdog detected non-announced service; attempting re-advertise
12:11:07 [plugins] bonjour: restarting advertiser (service stuck in probing for 235248ms)
12:11:07 [plugins] bonjour: advertised gateway fqdn=DESKTOP-6VFBFQR (OpenClaw)._openclaw-gw._tcp.local. host=openclaw.local. port=18789 state=unannounced
12:11:07 [openclaw] Unhandled promise rejection: CIAO PROBING CANCELLED
12:11:07 [openclaw] wrote stability bundle: C:\Users\DELL OPTIPLEX1i\.openclaw\logs\stability\openclaw-stability-2026-04-26T19-11-07-359Z-7848-unhandled_rejection.json

Additional warnings:

[model-pricing] OpenRouter pricing fetch failed (timeout 30s)
[model-pricing] LiteLLM pricing fetch failed (timeout 30s)
[ws] closed before connect code=1006
</details>
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

📋 Description

After updating OpenClaw from 2026.4.23 to 2026.4.24, the gateway no longer stays running. It appears to start successfully, but then crashes due to a Bonjour/ciao probing issue.

Steps to reproduce

🔁 Steps to Reproduce

Install/update OpenClaw:

npm install -g [email protected]

Run:

openclaw gateway run Wait ~2–5 minutes

Expected behavior

✅ Expected Behavior

openclaw gateway run should start and keep the gateway running normally.

Actual behavior

❌ Actual Behavior

The gateway initializes, loads plugins, and reports as “ready,” but after a few minutes:

Bonjour plugin gets stuck in probing Watchdog attempts restart

Process throws:

Unhandled promise rejection: CIAO PROBING CANCELLED Gateway exits back to PowerShell

OpenClaw version

OpenClaw version: 2026.4.24 (cbcfdf6)

Operating system

Windows 11 version 25

Install method

npm install -g [email protected]

Model

GPT 5.5

Provider / routing chain

Local Windows PowerShell → OpenClaw Gateway on 127.0.0.1:18789 → OpenAI provider/router → openai/gpt-5.5

Additional provider/model setup details

Local Windows PowerShell → OpenClaw Gateway on 127.0.0.1:18789 → OpenAI provider/router → openai/gpt-5.5

OpenClaw Gateway → OpenAI provider → model: openai/gpt-5.5

Logs, screenshots, and evidence

📄 Logs
<details> <summary>Click to expand logs</summary>
12:04:37 [gateway] ready (6 plugins: acpx, bonjour, browser, device-pair, phone-control, talk-voice; 94.4s)
12:04:37 [gateway] starting channels and sidecars...

12:07:12 [plugins] bonjour: watchdog detected non-announced service; attempting re-advertise
12:11:07 [plugins] bonjour: restarting advertiser (service stuck in probing for 235248ms)
12:11:07 [plugins] bonjour: advertised gateway fqdn=DESKTOP-6VFBFQR (OpenClaw)._openclaw-gw._tcp.local. host=openclaw.local. port=18789 state=unannounced
12:11:07 [openclaw] Unhandled promise rejection: CIAO PROBING CANCELLED
12:11:07 [openclaw] wrote stability bundle: C:\Users\DELL OPTIPLEX1i\.openclaw\logs\stability\openclaw-stability-2026-04-26T19-11-07-359Z-7848-unhandled_rejection.json

Additional warnings:

[model-pricing] OpenRouter pricing fetch failed (timeout 30s)
[model-pricing] LiteLLM pricing fetch failed (timeout 30s)
[ws] closed before connect code=1006
</details>

Impact and severity

Can Not start Openclaw gateway

Additional information

🧠 Notes / Possible Cause Issue appears tied to bonjour plugin / @homebridge/ciao Service gets stuck in probing state Restart logic triggers CIAO PROBING CANCELLED as an unhandled promise rejection Likely regression introduced in 2026.4.24

extent analysis

TL;DR

Downgrade OpenClaw to version 2026.4.23 to potentially resolve the gateway crashing issue caused by the Bonjour plugin.

Guidance

  • Verify that the issue is indeed related to the Bonjour plugin by checking the logs for the "CIAO PROBING CANCELLED" error message.
  • Attempt to reproduce the issue with a clean installation of OpenClaw 2026.4.24 to rule out any environmental factors.
  • Consider checking the @homebridge/ciao library for any known issues or updates that may be related to the probing state problem.
  • If downgrading to 2026.4.23 is not feasible, try to mitigate the issue by adjusting the watchdog settings or the Bonjour plugin configuration to prevent the service from getting stuck in probing state.

Example

No code snippet is provided as the issue seems to be related to a specific library or plugin, and modifying the code without further information may not be effective.

Notes

The issue appears to be a regression introduced in OpenClaw version 2026.4.24, and downgrading to the previous version may be the most straightforward solution. However, this may not be a long-term fix, and further investigation into the root cause of the issue is recommended.

Recommendation

Apply workaround: Downgrade to OpenClaw version 2026.4.23, as it is likely to resolve the gateway crashing issue caused by the Bonjour plugin. This is a temporary solution until the root cause of the issue is identified and fixed in a future version of OpenClaw.

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

✅ Expected Behavior

openclaw gateway run should start and keep the gateway running normally.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING