Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix v2026.4.24 regression: bonjour plugin crashes gateway on startup (mDNS/Zeroconf) [6 comments, 7 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#72152•Fetched 2026-04-27 05:34:05
View on GitHub
Comments
6
Participants
7
Timeline
10
Reactions
3
Author
ramshenoyramshenoy
Participants
clawsweeper[bot]clawsweeper[bot]dlxclemdlxclemDrShivangDrShivangKurtWolochKurtWolochmdiallognmdiallognnirhaunirhauramshenoyramshenoy
Timeline (top)
commented ×6cross-referenced ×3closed ×1

After upgrading from v2026.4.14 to v2026.4.24, the gateway fails to start due to a crash in the bonjour plugin (mDNS/Zeroconf local network discovery).

Root Cause

After upgrading from v2026.4.14 to v2026.4.24, the gateway fails to start due to a crash in the bonjour plugin (mDNS/Zeroconf local network discovery).

Fix Action

Workaround

Add to openclaw.json:

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

Code Example

{
  "plugins": {
    "entries": {
      "bonjour": {
        "enabled": false
      }
    }
  }
}
RAW_BUFFERClick to expand / collapse

Summary

After upgrading from v2026.4.14 to v2026.4.24, the gateway fails to start due to a crash in the bonjour plugin (mDNS/Zeroconf local network discovery).

Environment

  • OS: macOS Darwin 25.4.0 (arm64)
  • Hardware: Apple Mac Mini (Apple Silicon)
  • Previous version: v2026.4.14 (stable, no issues)
  • Upgraded to: v2026.4.24
  • Network: Home Wi-Fi (no companion devices actively pairing)

Steps to Reproduce

  1. Run openclaw update from v2026.4.14 to v2026.4.24
  2. Restart gateway via launchd: launchctl bootstrap gui/$UID ~/Library/LaunchAgents/ai.openclaw.gateway.plist
  3. Gateway fails to start — PID starts but health endpoint (/health) never responds
  4. Logs show bonjour plugin loading, then crash before Telegram initialization

Observed Behaviour

  • Gateway process starts (PID assigned) but /health never returns {"ok":true,"status":"live"}
  • Telegram channel never initializes (channel worked on v2026.4.14)
  • Disabling bonjour via config (plugins.entries.bonjour.enabled: false) resolves the crash immediately
  • After disabling bonjour: gateway starts cleanly, Telegram works, crons fire normally

Expected Behaviour

Gateway should start successfully with bonjour plugin enabled (as it did on v2026.4.14).

Workaround

Add to openclaw.json:

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

Impact

  • bonjour is used for local companion app discovery (iPhone/iPad pairing on same Wi-Fi)
  • Telegram, crons, memory, tools — all unaffected once bonjour disabled
  • Any user upgrading to v2026.4.24 with bonjour enabled (default) will hit this crash

Additional Context

  • Fleet: 15 agent instances, all on same binary — all affected by same regression
  • This was caught during a coordinated fleet upgrade; single-instance users may also be silently affected if they rely on launchd auto-restart masking the crash loop

extent analysis

TL;DR

Disable the bonjour plugin by setting plugins.entries.bonjour.enabled to false in openclaw.json to prevent the gateway from crashing after upgrading to v2026.4.24.

Guidance

  • Verify that the bonjour plugin is the cause of the crash by checking the logs for the plugin loading and then crashing before Telegram initialization.
  • Disable the bonjour plugin as a temporary workaround to allow the gateway to start and function normally, except for local companion app discovery.
  • Consider testing the gateway with the bonjour plugin enabled on a different network or environment to see if the issue is specific to the current setup.
  • Review the changelog for v2026.4.24 to see if there are any known issues or changes related to the bonjour plugin.

Example

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

This is an example of how to disable the bonjour plugin in openclaw.json.

Notes

The root cause of the issue is not explicitly stated, but it appears to be related to the bonjour plugin. Disabling the plugin allows the gateway to start and function normally, but it may not be a permanent solution.

Recommendation

Apply the workaround by disabling the bonjour plugin, as it allows the gateway to function normally and does not appear to have any significant impact on other features.

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…
#device allocation#model download#tokenizer error#prompt formatting#chain 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 v2026.4.24 regression: bonjour plugin crashes gateway on startup (mDNS/Zeroconf) [6 comments, 7 participants]