Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Gateway crashes on startup in 4.24 on WSL (CIAO ANNOUNCEMENT CANCELLED unhandled rejection from Bonjour plugin) [1 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#72103•Fetched 2026-04-27 05:34:50
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
1
Author
NicholasPapaNicholasPapa
Participants
clawsweeper[bot]clawsweeper[bot]NicholasPapaNicholasPapa
Timeline (top)
cross-referenced ×3closed ×1commented ×1

Error Message

This is a regression introduced in cb4fc58547 (feat(plugins): move Bonjour discovery into bundled plugin, Apr 23). When Bonjour was extracted into a bundled plugin, the advertiser restart cycle lost proper error containment for the CIAO ANNOUNCEMENT CANCELLED rejection in multicast-blocked environments (WSL2, containers).

Root Cause

Root cause (traced from source)

Fix Action

Fix / Workaround

Workaround (confirmed working)

Consider a 4.24.1 patch release (or note this in 4.24 release notes) to ship ca0232ff0e for users on WSL who cannot update to a newer build immediately.

Reported via AI-assisted debugging session. Crash confirmed on a real WSL2 + Tailscale serve setup. Workaround validated.

RAW_BUFFERClick to expand / collapse

Environment

  • OpenClaw 2026.4.24 (cbcfdf6)
  • Node: runtime default
  • WSL2 (Ubuntu), gateway bind: loopback, Tailscale Serve via WSL-native ailscale serve
  • No systemd unit — gateway started via openclaw gateway

Observed

Gateway starts, reaches eady state, then exits immediately (~25s after start) with an unhandled promise rejection:

\
18:04:39 [plugins] bonjour: watchdog detected non-announced service; attempting re-advertise (... state=probing) 18:04:43 [plugins] bonjour: advertised gateway ... state=announcing 18:04:55 [plugins] bonjour: restarting advertiser (service stuck in announcing for 16237ms (... state=announcing)) 18:04:55 [openclaw] Unhandled promise rejection: CIAO ANNOUNCEMENT CANCELLED 18:04:55 [openclaw] wrote stability bundle: .../openclaw-stability-...-unhandled_rejection.json \\

Process exits. Gateway is completely non-functional.

Root cause (traced from source)

This is a regression introduced in cb4fc58547 (feat(plugins): move Bonjour discovery into bundled plugin, Apr 23). When Bonjour was extracted into a bundled plugin, the advertiser restart cycle lost proper error containment for the CIAO ANNOUNCEMENT CANCELLED rejection in multicast-blocked environments (WSL2, containers).

In 4.15 the Bonjour stall (#69011) was non-fatal — a delay on startup. In 4.24 it escalates to a full process crash.

The fix is already in main as ca0232ff0e (fix(bonjour): bound stuck advertiser restarts, Apr 26), which adds MAX_CONSECUTIVE_RESTARTS = 3 and graceful self-disable. It is not included in the 4.24 release.

Workaround (confirmed working)

\\ash openclaw plugins disable bonjour \\

Gateway stays up normally after this. Users on WSL who use Tailscale don't need mDNS/Bonjour anyway.

Suggested action

Consider a 4.24.1 patch release (or note this in 4.24 release notes) to ship ca0232ff0e for users on WSL who cannot update to a newer build immediately.

Related

  • #69011 — original Bonjour stall issue (4.15, non-fatal, now closed)
  • cb4fc58547 — the plugin migration that introduced the regression
  • ca0232ff0e — the fix (merged main, not in 4.24)

Reported via AI-assisted debugging session. Crash confirmed on a real WSL2 + Tailscale serve setup. Workaround validated.

extent analysis

TL;DR

Disable the Bonjour plugin using openclaw plugins disable bonjour to prevent the gateway from crashing due to an unhandled promise rejection.

Guidance

  • The issue is caused by a regression introduced in version 2026.4.24, which can be mitigated by disabling the Bonjour plugin.
  • To verify the workaround, start the gateway after disabling the Bonjour plugin and check if it remains functional.
  • If possible, consider updating to a newer build that includes the fix (ca0232ff0e) to resolve the issue permanently.
  • Note that users on WSL who use Tailscale may not need mDNS/Bonjour, making the workaround a viable long-term solution.

Example

No code snippet is necessary, as the workaround is a simple command: openclaw plugins disable bonjour.

Notes

The fix for this issue is already available in the main branch (ca0232ff0e), but it is not included in the 4.24 release. A 4.24.1 patch release or a note in the 4.24 release notes may be necessary to inform users of the workaround.

Recommendation

Apply the workaround by disabling the Bonjour plugin, as it is a simple and effective solution that can prevent the gateway from crashing. This is especially suitable for users on WSL who do not require mDNS/Bonjour functionality.

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…
#docker error#permission error#memory optimization#batch processing#GPU compatibility

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 [Bug]: Gateway crashes on startup in 4.24 on WSL (CIAO ANNOUNCEMENT CANCELLED unhandled rejection from Bonjour plugin) [1 comments, 2 participants]