Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Bonjour plugin crash loop on gateway startup (v2026.4.24 regression) [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#72307•Fetched 2026-04-27 05:31:51
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
rafaelfaleirorafaelfaleiro
Participants
clawsweeper[bot]clawsweeper[bot]rafaelfaleirorafaelfaleiro
Timeline (top)
closed ×1commented ×1cross-referenced ×1

After upgrading from 2026.4.12 to 2026.4.24, the gateway enters a crash loop on every startup due to an unhandled promise rejection in the bonjour plugin. The gateway restarts via systemd every ~1-2 minutes but crashes again consistently.

Error Message

The bundle was generated (reason: unhandled_rejection) but contains no stack trace — only process metadata (pid, platform, node version, uptime). No additional error detail was captured.

Root Cause

After upgrading from 2026.4.12 to 2026.4.24, the gateway enters a crash loop on every startup due to an unhandled promise rejection in the bonjour plugin. The gateway restarts via systemd every ~1-2 minutes but crashes again consistently.

Fix Action

Workaround

openclaw plugins disable bonjour
openclaw gateway restart

Gateway runs stable with bonjour disabled.

Code Example

[gateway] ready (7 plugins: acpx, bonjour, browser, device-pair, phone-control, talk-voice, telegram)
[gateway] starting channels and sidecars...
[plugins] bonjour: watchdog detected non-announced service; attempting re-advertise (state=probing)
[plugins] bonjour: restarting advertiser (service stuck in probing for ~15000ms, state=probing)
[plugins] bonjour: advertised gateway (state=unannounced)
[openclaw] Unhandled promise rejection: CIAO PROBING CANCELLED
[openclaw] wrote stability bundle: .openclaw/logs/stability/openclaw-stability-<timestamp>-<pid>-unhandled_rejection.json

---

openclaw plugins disable bonjour
openclaw gateway restart
RAW_BUFFERClick to expand / collapse

Description

After upgrading from 2026.4.12 to 2026.4.24, the gateway enters a crash loop on every startup due to an unhandled promise rejection in the bonjour plugin. The gateway restarts via systemd every ~1-2 minutes but crashes again consistently.

Environment

  • Version: 2026.4.24 (cbcfdf6)
  • Last stable version: 2026.4.12 (1c0672b)
  • OS: Ubuntu Linux, x64
  • Node: v24.14.1

Log sequence (reproduced on every restart)

[gateway] ready (7 plugins: acpx, bonjour, browser, device-pair, phone-control, talk-voice, telegram)
[gateway] starting channels and sidecars...
[plugins] bonjour: watchdog detected non-announced service; attempting re-advertise (state=probing)
[plugins] bonjour: restarting advertiser (service stuck in probing for ~15000ms, state=probing)
[plugins] bonjour: advertised gateway (state=unannounced)
[openclaw] Unhandled promise rejection: CIAO PROBING CANCELLED
[openclaw] wrote stability bundle: .openclaw/logs/stability/openclaw-stability-<timestamp>-<pid>-unhandled_rejection.json

Stability bundle

The bundle was generated (reason: unhandled_rejection) but contains no stack trace — only process metadata (pid, platform, node version, uptime). No additional error detail was captured.

Impact

Gateway becomes unreachable. TUI shows gateway disconnected immediately after connecting. The crash loop repeats indefinitely via systemd restarts.

Workaround

openclaw plugins disable bonjour
openclaw gateway restart

Gateway runs stable with bonjour disabled.

Regression

Did not occur on 2026.4.12. Appeared immediately after upgrade to 2026.4.24. The bonjour plugin was working correctly on the previous version.

extent analysis

TL;DR

Disabling the bonjour plugin resolves the crash loop issue, suggesting a problem with the plugin's interaction in the new version.

Guidance

  • The crash loop is caused by an unhandled promise rejection in the bonjour plugin, indicating a potential issue with the plugin's implementation or compatibility with version 2026.4.24.
  • Disabling the bonjour plugin, as shown in the provided workaround, allows the gateway to run stably, confirming the plugin as the source of the problem.
  • To further diagnose, review the bonjour plugin's documentation and code for any changes or known issues related to version 2026.4.24.
  • Consider reporting the issue to the plugin maintainers or seeking an updated version of the bonjour plugin that is compatible with 2026.4.24.

Example

No code snippet is necessary as the workaround is provided in the issue description.

Notes

The exact cause of the unhandled promise rejection within the bonjour plugin is not specified, and without a stack trace, pinpointing the issue is challenging. The stability bundle's lack of detailed error information limits further analysis.

Recommendation

Apply the workaround by disabling the bonjour plugin until a compatible or updated version is available, as it immediately resolves the crash loop issue and allows the gateway to function.

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…
#api#ssr#installation#tensor shape#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