openclaw - 💡(How to fix) Fix [Bug]: Gateway crash after upgrade to 2026.4.24 [3 comments, 2 participants]

Gateway start blocked: existing config is missing gateway.mode. Treat this as suspicious or clobbered config. Re-run openclaw onboard --mode local or openclaw setup, set gateway.mode=local manually, or pass --allow-unconfigured.

Config write audit: C:\Users\imagine.openclaw\logs\config-audit.jsonl

Config overwrite: C:\Users\imagine.openclaw\openclaw.json (...)

security warning: dangerous config flags enabled: gateway.controlUi.allowInsecureAuth=true. Run openclaw security audit.

OpenRouter pricing fetch failed (timeout 30s): TimeoutError: The operation was aborted due to timeout

LiteLLM pricing fetch failed (timeout 30s): TimeoutError: The operation was aborted due to timeout

bonjour: watchdog detected non-announced service; attempting re-advertise (...)

bonjour: restarting advertiser (service stuck in probing ...)

[openclaw] Unhandled promise rejection: CIAO PROBING CANCELLED

[openclaw] wrote stability bundle: C:\Users\imagine.openclaw\logs\stability...unhandled_rejection.json

TL;DR

The gateway crash after upgrading to 2026.4.24 may be due to a missing or misconfigured gateway.mode setting, and setting it to local manually or re-running the onboarding process might resolve the issue.

Guidance

• Verify the gateway.mode setting in the openclaw.json configuration file to ensure it is correctly set to local or another appropriate mode.
• Try re-running the onboarding process using openclaw onboard --mode local to reconfigure the gateway settings.
• Check the config-audit.jsonl log file for any configuration overwrite or audit issues that might be related to the gateway crash.
• Review the security warnings and consider running openclaw security audit to address any potential security concerns.

Example

No specific code snippet is provided, but the command openclaw onboard --mode local can be used to reconfigure the gateway settings.

Notes

The issue seems to be related to the gateway.mode setting, but the root cause might be more complex, and additional debugging or configuration changes might be necessary to fully resolve the issue.

Recommendation

Apply workaround: set gateway.mode=local manually or re-run the onboarding process using openclaw onboard --mode local, as this is the most direct and likely solution based on the provided logs and error messages.