openclaw - 💡(How to fix) Fix [Bug]: OpenClaw 2026.4.24: gateway crash loop caused by bonjour/mDNS discovery (CIAO PROBING/ANNOUNCEMENT CANCELLED) [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#71821Fetched 2026-04-26 05:07:50
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×2closed ×1commented ×1

After upgrading to OpenClaw 2026.4.24, the gateway entered a crash loop shortly after startup.

While the loop was active:

  • the local web dashboard was unavailable
  • Telegram connectivity was unavailable
  • systemd kept restarting the gateway service

The crash appears to be caused by the bonjour/mDNS discovery path (@homebridge/ciao) throwing unhandled promise rejections during advertiser probing/announcement.

Error Message

Typical sequence:

  1. Gateway starts normally
  2. HTTP server and plugins come up
  3. Bonjour watchdog detects a stuck/non-announced service
  4. Advertiser restarts
  5. Unhandled rejection is thrown
  6. Gateway exits with status 1
  7. systemd restarts the service

Root Cause

The crash appears to be caused by the bonjour/mDNS discovery path (@homebridge/ciao) throwing unhandled promise rejections during advertiser probing/announcement.

Fix Action

Workaround

A systemd override stabilized the service:

[Service]
Environment=OPENCLAW_DISABLE_BONJOUR=1

Code Example

[Service]
Environment=OPENCLAW_DISABLE_BONJOUR=1


### Steps to reproduce

After restart with this override:

• gateway remained running
• dashboard returned HTTP 200
Telegram resumed normal operation
• no new CIAO / bonjour crash events appeared

### Expected behavior

If bonjour/mDNS advertisement fails, the gateway should degrade gracefully and continue running. Discovery failure should not take down the entire gateway.

### Actual behavior

Failure in bonjour discovery causes an unhandled promise rejection that crashes the whole gateway process.

Suggested direction

Catch and contain @homebridge/ciao advertiser cancellation/restart errors
Prevent bonjour discovery failures from crashing the gateway
Consider auto-disabling bonjour after repeated advertiser failures
Consider not listing bonjour in ready (...) output when it is disabled by env override

I have a support diagnostics export zip prepared and can attach it to the issue.

### OpenClaw version

OpenClaw 2026.4.24

### Operating system

Ubuntu 24.04

### Install method

npm global

### Model

openai-codex/gpt-5.4

### Provider / routing chain

openclaw -> openai

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence
RAW_BUFFERClick to expand / collapse

Bug type

Crash (process/app exits or hangs)

Beta release blocker

No

Summary

After upgrading to OpenClaw 2026.4.24, the gateway entered a crash loop shortly after startup.

While the loop was active:

  • the local web dashboard was unavailable
  • Telegram connectivity was unavailable
  • systemd kept restarting the gateway service

The crash appears to be caused by the bonjour/mDNS discovery path (@homebridge/ciao) throwing unhandled promise rejections during advertiser probing/announcement.

Environment

  • OpenClaw version: 2026.4.24
  • OS: Linux
  • Node: 22.22.0
  • Service type: systemd user service
  • Gateway mode: local
  • Bind: 127.0.0.1
  • Port: 18789

User-visible impact

  • Could not open the web dashboard after update
  • Telegram stopped working while the gateway was crash-looping
  • Gateway repeatedly restarted under systemd

Observed behavior

Typical sequence:

  1. Gateway starts normally
  2. HTTP server and plugins come up
  3. Bonjour watchdog detects a stuck/non-announced service
  4. Advertiser restarts
  5. Unhandled rejection is thrown
  6. Gateway exits with status 1
  7. systemd restarts the service

Key log evidence

Observed in journalctl --user -u openclaw-gateway.service and /tmp/openclaw/openclaw-2026-04-25.log:

  • bonjour: watchdog detected non-announced service; attempting re-advertise
  • bonjour: restarting advertiser (service stuck in probing ...)
  • bonjour: restarting advertiser (service stuck in announcing ...)
  • Unhandled promise rejection: CIAO PROBING CANCELLED
  • Unhandled promise rejection: CIAO ANNOUNCEMENT CANCELLED
  • openclaw-gateway.service: Main process exited, code=exited, status=1/FAILURE

Example:

  • 2026-04-25T22:32:42+00:00 [openclaw] Unhandled promise rejection: CIAO ANNOUNCEMENT CANCELLED
  • 2026-04-25T22:32:42+00:00 openclaw-gateway.service: Main process exited, code=exited, status=1/FAILURE
  • 2026-04-25T22:33:24+00:00 [openclaw] Unhandled promise rejection: CIAO PROBING CANCELLED
  • 2026-04-25T22:33:24+00:00 openclaw-gateway.service: Main process exited, code=exited, status=1/FAILURE

Configuration findings

  • openclaw.json was not corrupted
  • openclaw.json.last-good matched the active config
  • Telegram auth/token did not appear to be the cause
  • Gateway bind/port remained correct

Workaround

A systemd override stabilized the service:

[Service]
Environment=OPENCLAW_DISABLE_BONJOUR=1


### Steps to reproduce

After restart with this override:

• gateway remained running
• dashboard returned HTTP 200
• Telegram resumed normal operation
• no new CIAO / bonjour crash events appeared

### Expected behavior

If bonjour/mDNS advertisement fails, the gateway should degrade gracefully and continue running. Discovery failure should not take down the entire gateway.

### Actual behavior

Failure in bonjour discovery causes an unhandled promise rejection that crashes the whole gateway process.

Suggested direction

• Catch and contain @homebridge/ciao advertiser cancellation/restart errors
• Prevent bonjour discovery failures from crashing the gateway
• Consider auto-disabling bonjour after repeated advertiser failures
• Consider not listing bonjour in ready (...) output when it is disabled by env override

I have a support diagnostics export zip prepared and can attach it to the issue.

### OpenClaw version

OpenClaw 2026.4.24

### Operating system

Ubuntu 24.04

### Install method

npm global

### Model

openai-codex/gpt-5.4

### Provider / routing chain

openclaw -> openai

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence

```shell

Impact and severity

No response

Additional information

openclaw-bug-2026-4-24-bonjour.zip

extent analysis

TL;DR

Disable bonjour/mDNS discovery by setting the OPENCLAW_DISABLE_BONJOUR environment variable to 1 to prevent the gateway from crashing.

Guidance

  • Identify the root cause of the unhandled promise rejections in the @homebridge/ciao advertiser probing/announcement.
  • Consider catching and containing advertiser cancellation/restart errors to prevent the gateway from crashing.
  • Implement a fallback mechanism to auto-disable bonjour after repeated advertiser failures.
  • Verify that the gateway remains running and functional after disabling bonjour by checking the dashboard and Telegram connectivity.

Example

[Service]
Environment=OPENCLAW_DISABLE_BONJOUR=1

This systemd override can be used to disable bonjour and stabilize the service.

Notes

The provided workaround suggests that disabling bonjour resolves the issue, but it may not be a permanent solution. Further investigation into the root cause of the unhandled promise rejections is necessary to implement a more robust fix.

Recommendation

Apply the workaround by setting OPENCLAW_DISABLE_BONJOUR=1 to prevent the gateway from crashing, and investigate the root cause of the unhandled promise rejections to implement a more permanent solution.

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

If bonjour/mDNS advertisement fails, the gateway should degrade gracefully and continue running. Discovery failure should not take down the entire gateway.

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]: OpenClaw 2026.4.24: gateway crash loop caused by bonjour/mDNS discovery (CIAO PROBING/ANNOUNCEMENT CANCELLED) [1 comments, 2 participants]