Protocol mismatch happens when trying to resume or do a new chat session via clawsuite with newer openclaw versions.
Example from gateway log:
10:59:19 [ws] closed before connect conn=26410a62-6d2c-4acf-b86b-26f4b2b44886 peer=127.0.0.1:56969->127.0.0.1:18789 remote=127.0.0.1 fwd=n/a origin=http://127.0.0.1:18789 host=127.0.0.1:18789 ua=n/a code=1006 reason=n/a
10:59:20 [ws] protocol mismatch conn=318cd664-1bcc-45fe-8b4d-666ff30643b0 peer=127.0.0.1:56972->127.0.0.1:18789 remote=127.0.0.1 remotePort=56972 client=clawsuite ui vdev min=3 max=3 expected=4 probeMin=4 instance=65a931f7-553e-42b8-b059-6505127961a7
Clawsuite 4 vite log:
clawsuite@4.0.0 dev
cross-env NODE_OPTIONS="--max-old-space-size=2048" vite dev --port 3000
VITE v7.3.5 ready in 3864 ms
➜ Local: http://127.0.0.1:3000/
➜ press h + enter to show help
[vite] connected.
(node:13088) Warning: --localstorage-file was provided without a valid path
(Use node --trace-warnings ... to show where the warning was created)
[gateway] RPC timeout after 30000ms for status (1/15)
[gateway] RPC timeout after 30000ms for sessions.list (2/15)
[gateway] RPC timeout after 30000ms for sessions.list (3/15)
[gateway] RPC timeout after 30000ms for models.list (4/15)
[gateway] RPC timeout after 30000ms for chat.history (5/15)
[gateway] RPC timeout after 30000ms for cron.list (6/15)
[gateway] RPC timeout after 30000ms for usage.cost (7/15)
[gateway] RPC timeout after 30000ms for sessions.patch (8/15)
[gateway] RPC timeout after 30000ms for sessions.resolve (9/15)
[gateway] RPC timeout after 30000ms for chat.history (10/15)
[gateway] RPC timeout after 30000ms for sessions.generateTitle (11/15)
[gateway] RPC timeout after 30000ms for sessions.list (12/15)
[gateway] RPC timeout after 30000ms for cron.jobs.list (13/15)
[gateway] RPC timeout after 30000ms for sessions.list (14/15)
[gateway] Circuit breaker OPEN after 15 consecutive timeouts (last: sessions.lis
t)
[gateway] Circuit breaker OPEN after 16 consecutive timeouts (last: sessions.lis
t)
[gateway] Circuit breaker OPEN after 17 consecutive timeouts (last: sessions.res
olve)
[/api/send] Error: Gateway circuit breaker open (17 consecutive failures, coolin
g down)
[gateway] Circuit breaker OPEN after 18 consecutive timeouts (last: chat.history
)
[gateway] Circuit breaker OPEN after 19 consecutive timeouts (last: scheduler.jo
bs.list)
Protocol mismatch happens when trying to resume or do a new chat session via clawsuite with newer openclaw versions.
Example from gateway log:
10:59:19 [ws] closed before connect conn=26410a62-6d2c-4acf-b86b-26f4b2b44886 peer=127.0.0.1:56969->127.0.0.1:18789 remote=127.0.0.1 fwd=n/a origin=http://127.0.0.1:18789 host=127.0.0.1:18789 ua=n/a code=1006 reason=n/a
10:59:20 [ws] protocol mismatch conn=318cd664-1bcc-45fe-8b4d-666ff30643b0 peer=127.0.0.1:56972->127.0.0.1:18789 remote=127.0.0.1 remotePort=56972 client=clawsuite ui vdev min=3 max=3 expected=4 probeMin=4 instance=65a931f7-553e-42b8-b059-6505127961a7
Clawsuite 4 vite log:
VITE v7.3.5 ready in 3864 ms
➜ Local: http://127.0.0.1:3000/
➜ press h + enter to show help
[vite] connected.
(node:13088) Warning:
--localstorage-filewas provided without a valid path(Use
node --trace-warnings ...to show where the warning was created)[gateway] RPC timeout after 30000ms for status (1/15)
[gateway] RPC timeout after 30000ms for sessions.list (2/15)
[gateway] RPC timeout after 30000ms for sessions.list (3/15)
[gateway] RPC timeout after 30000ms for models.list (4/15)
[gateway] RPC timeout after 30000ms for chat.history (5/15)
[gateway] RPC timeout after 30000ms for cron.list (6/15)
[gateway] RPC timeout after 30000ms for usage.cost (7/15)
[gateway] RPC timeout after 30000ms for sessions.patch (8/15)
[gateway] RPC timeout after 30000ms for sessions.resolve (9/15)
[gateway] RPC timeout after 30000ms for chat.history (10/15)
[gateway] RPC timeout after 30000ms for sessions.generateTitle (11/15)
[gateway] RPC timeout after 30000ms for sessions.list (12/15)
[gateway] RPC timeout after 30000ms for cron.jobs.list (13/15)
[gateway] RPC timeout after 30000ms for sessions.list (14/15)
[gateway] Circuit breaker OPEN after 15 consecutive timeouts (last: sessions.lis
t)
[gateway] Circuit breaker OPEN after 16 consecutive timeouts (last: sessions.lis
t)
[gateway] Circuit breaker OPEN after 17 consecutive timeouts (last: sessions.res
olve)
[/api/send] Error: Gateway circuit breaker open (17 consecutive failures, coolin
g down)
[gateway] Circuit breaker OPEN after 18 consecutive timeouts (last: chat.history
)
[gateway] Circuit breaker OPEN after 19 consecutive timeouts (last: scheduler.jo
bs.list)