启用 TLS 后，CLI probeUrl 需切换 wss 以避免误判离线
该修复聚焦于 TLS 网关探测协议错误：若仍用 ws，会导致健康探测和连通性判断偏差。可直接沉淀为上线检查清单。
GITHUBDiscovered 2026-02-12Author tha80
Prerequisites
- Gateway TLS is enabled (HTTPS/WSS) and CLI relies on probeUrl for connectivity checks.
- You can run staging smoke tests before production rollout.
Steps
- Audit current probeUrl values in deployment scripts and environment configs.
- For TLS-enabled gateways, replace ws:// probe endpoints with wss:// explicitly.
- Run CLI connectivity checks in staging and compare before/after false-negative rate.
- Add CI lint rule to reject ws:// probeUrl when tls=true in config templates.
Commands
openclaw gateway statusopenclaw helpgrep -R "probeUrl" -n .Verify
With TLS on, probe checks stay green using wss and no longer flap between online/offline.
Caveats
- Exact config key path may vary across versions and wrappers（需验证）.
- Reverse proxies may require additional websocket headers/timeouts.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗