Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Bonjour crash loop STILL breaking gateway in 2026.4.24 — stop shipping broken defaults [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#71814•Fetched 2026-04-26 05:07:54
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
4
Author
amdhelperamdhelper
Participants
amdhelperamdhelpersteipetesteipete
Timeline (top)
closed ×1commented ×1cross-referenced ×1subscribed ×1

Root Cause

I just spent an afternoon debugging gateway crashes on two separate servers (Debian 13/PVE and a VPS) after upgrading to 2026.4.24. Root cause: the bonjour plugin throws Unhandled promise rejection: CIAO ANNOUNCEMENT CANCELLED and kills the process. The systemd service restarts, it crashes again, repeat forever.

RAW_BUFFERClick to expand / collapse

The Situation

I just spent an afternoon debugging gateway crashes on two separate servers (Debian 13/PVE and a VPS) after upgrading to 2026.4.24. Root cause: the bonjour plugin throws Unhandled promise rejection: CIAO ANNOUNCEMENT CANCELLED and kills the process. The systemd service restarts, it crashes again, repeat forever.

This is not a new bug. A quick search shows at least 5 open issues reporting the same thing going back to early April:

  • #64484 (Apr 11) — Bonjour flapping loop
  • #63153 (Apr 8) — Bonjour stall triggers restart loop
  • #69011 (Apr 22) — Watchdog restart loop
  • #69693 (Apr 21) — WSL2 crash
  • #64928 (Apr 18) — WebSocket path wedged

And several more closed as "duplicate" in the last 48 hours (#71751, #71769, #71771, #71781).

The Problem

You are shipping a plugin that crashes the gateway process as a default-enabled component. This is not a minor cosmetic issue — it is a crash loop that takes down the entire service.

Closing reports as "duplicate" while the root cause remains unfixed in every release is not bug triage, it is issue laundering.

What I Had to Do

On each server, I had to:

  1. SSH in as root
  2. Manually edit /root/.openclaw/openclaw.json
  3. Add "bonjour": {"enabled": false} to plugins.entries
  4. Kill the gateway and let systemd restart it

This should not be necessary. A plugin that crashes the process should not be enabled by default.

What You Should Do

  1. Immediately: Disable bonjour by default until the underlying ciao library issue is fixed
  2. Short-term: Add an unhandled rejection handler so a plugin crash does not take down the entire gateway
  3. Actually fix it: The ciao library has been throwing these cancellation errors for weeks. Either fix the upstream or replace it.

Environment

  • OpenClaw 2026.4.24 (cbcfdf6)
  • Node 24.14.1
  • Linux 6.17.13-3-pve / 6.17.13-1-pve (Debian 13)
  • Gateway: local mode, loopback bind
  • Crash: Unhandled promise rejection: CIAO ANNOUNCEMENT CANCELLED in bonjour plugin

extent analysis

TL;DR

Disable the bonjour plugin by default to prevent the gateway crash loop until the underlying issue is fixed.

Guidance

  • Verify that disabling the bonjour plugin resolves the crash loop by checking the gateway logs and systemd service status after applying the change.
  • Consider adding an unhandled rejection handler to prevent plugin crashes from taking down the entire gateway.
  • Review the ciao library issues and either fix the upstream or replace it to address the root cause of the problem.
  • Check for any other plugins that may be affected by similar issues and consider disabling them temporarily.

Example

To disable the bonjour plugin, add the following configuration to /root/.openclaw/openclaw.json:

"plugins": {
  "entries": {
    "bonjour": {
      "enabled": false
    }
  }
}

Notes

The issue is not specific to a particular environment, as it has been reported on multiple servers with different configurations. Disabling the bonjour plugin is a temporary workaround until the underlying issue is fixed.

Recommendation

Apply workaround: Disable the bonjour plugin by default to prevent the gateway crash loop, as it is a critical issue that takes down the entire service.

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

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 Bonjour crash loop STILL breaking gateway in 2026.4.24 — stop shipping broken defaults [1 comments, 2 participants]