#CLI ALways Times Out
1 messages · Page 1 of 1 (latest)
Let me verify this against the docs and source, the mDNS bit is interesting and might be a red herring.
I checked the docs and source on this one.
What your log means is pretty specific: the gateway sends connect.challenge immediately on socket open, and the CLI never answers it before the pre-auth handshake times out. So this is not primarily a pairing/token problem.
A few useful bits:
webchat works, CLI times outpoints to the CLI handshake path specifically- the repeated Bonjour/mDNS
announcingloop is probably not the auth path, but it is suspicious gateway churn on Windows 2026.4.9already includes the earlier Windows slow-startup handshake fix, so I would not assume “just update” is the whole answer here
What I’d try first:
- Disable Bonjour/mDNS completely and restart
In your config:{
discovery: {
mdns: { mode: "off" }
}
}
or use OPENCLAW_DISABLE_BONJOUR=1, then:
openclaw gateway restart
- Run the built-in diagnostics
openclaw gateway status openclaw status --all openclaw logs --follow