openclaw - 💡(How to fix) Fix Bonjour advertiser stuck in "announcing" state [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#74977Fetched 2026-05-01 05:39:20
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
2
Author
Timeline (top)
labeled ×2closed ×1commented ×1

The internal bonjour/mDNS advertiser repeatedly gets stuck in "announcing" state and restarts every ~40 seconds, causing log spam.

Error Message

  • Already tried setting gateway.bind to "lan" but that's incompatible with tailscale.mode=serve (validation error)

Root Cause

The internal bonjour/mDNS advertiser repeatedly gets stuck in "announcing" state and restarts every ~40 seconds, causing log spam.

Code Example

20:07:45+12:00 [bonjour] restarting advertiser (service stuck in announcing for 41520ms (gateway fqdn=Win11-openClaw._openclaw-gw._tcp.local. host=openclaw.local. port=18789 state=announcing))
20:07:45+12:00 [ws] handshake timeout conn=96502ba7-5b07-4576-94c0-c84336dce8a2 remote=127.0.0.1
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

The internal bonjour/mDNS advertiser repeatedly gets stuck in "announcing" state and restarts every ~40 seconds, causing log spam.

Steps to reproduce

  1. starting openclaw 2026.4.1 in native Windows - newer release notes have no mention of this issue
  2. This happens on every gateway start, with the advertiser repeatedly restarting every ~40 seconds.

Expected behavior

  • Bonjour advertiser should successfully announce and transition to "announced" state
  • Should not get stuck in "announcing" indefinitely

Actual behavior

20:07:45+12:00 [bonjour] restarting advertiser (service stuck in announcing for 41520ms (gateway fqdn=Win11-openClaw._openclaw-gw._tcp.local. host=openclaw.local. port=18789 state=announcing)) 20:07:45+12:00 [ws] handshake timeout conn=96502ba7-5b07-4576-94c0-c84336dce8a2 remote=127.0.0.1

OpenClaw version

OpenClaw: 2026.4.1

Operating system

OS: Windows (Win11-openClaw)

Install method

npm global

Model

minimax2

Provider / routing chain

openclaw/ollama/minimax

Additional provider/model setup details

No response

Logs, screenshots, and evidence

20:07:45+12:00 [bonjour] restarting advertiser (service stuck in announcing for 41520ms (gateway fqdn=Win11-openClaw._openclaw-gw._tcp.local. host=openclaw.local. port=18789 state=announcing))
20:07:45+12:00 [ws] handshake timeout conn=96502ba7-5b07-4576-94c0-c84336dce8a2 remote=127.0.0.1

Impact and severity

This is an unwanted function with no obvious way to disable

Additional information

  • Already tried setting gateway.bind to "lan" but that's incompatible with tailscale.mode=serve (validation error)
  • The plugins.bonjour.enabled: false config is present but appears to be a stale entry (plugin not found)
  • This is not related to Apple's Bonjour service (no mDNSResponder process running)
  • This appears to be OpenClaw's internal mDNS advertiser implementation

extent analysis

TL;DR

The internal Bonjour/mDNS advertiser in OpenClaw 2026.4.1 gets stuck in the "announcing" state and restarts every 40 seconds, causing log spam, and may require configuration adjustments or updates to resolve.

Guidance

  • Investigate the gateway.bind configuration option further, as setting it to "lan" was attempted but resulted in a validation error with tailscale.mode=serve. Finding an alternative configuration that works with both settings might resolve the issue.
  • Since plugins.bonjour.enabled: false is present but appears stale, try removing or updating this configuration to ensure it's properly disabled or configured, as it might interfere with the internal mDNS advertiser.
  • Review OpenClaw's documentation or community forums for any known issues or workarounds related to the internal mDNS advertiser, especially considering the specific version 2026.4.1 and the operating system (Windows).
  • Consider checking for any updates to OpenClaw that might address this issue, as the release notes for version 2026.4.1 do not mention this problem.

Example

No specific code example can be provided without more context on the configuration files or codebase of OpenClaw. However, ensuring that the configuration settings are correctly applied and compatible with each other is crucial.

Notes

The issue seems specific to the internal implementation of the mDNS advertiser in OpenClaw and not related to Apple's Bonjour service. The provided logs indicate a restart of the advertiser due to it getting stuck, which suggests a potential issue with the service's state management or configuration.

Recommendation

Apply workaround: Given the information, the best course of action seems to be trying different configuration settings, especially focusing on the gateway.bind and plugins.bonjour.enabled options, to find a combination that works without causing the mDNS advertiser to get stuck in the "announcing" state.

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

  • Bonjour advertiser should successfully announce and transition to "announced" state
  • Should not get stuck in "announcing" indefinitely

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 advertiser stuck in "announcing" state [1 comments, 2 participants]