Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
After upgrading OpenClaw to Version 2026.5.12, the gateway became unusable for me. I had left the browser open, but instead of reconnecting to the gateway, it just reported a "protocol mismatch". So I again pointed the browser (MS Edge) at the address given on top of the output in the command window, "http://127.0.0.1:18791/", but it just shows the word "Unauthorized". The logfile itself reports a "protocol mismatch", later all used models time out.
System data:
Operating system: Windows 10
Browser: MS Edge
Default model: xiaomi/mimo-v2.5-pro
Steps to reproduce
- Update OpenClaw on Windows 10 to newest version via npm
- Start Gateway
- Point browser to the given address
Expected behavior
Normally, the Gateway should start up, and after at most 1-2 minutes, the chat window should appear with the agent ready to accept commands or discussions.
Actual behavior
The Gateway only shows the word "Unauthorized".
OpenClaw version
2026.5.12
Operating system
Windows 10
Install method
npm
Model
xiaomi/mimo-v2.5-pro
Provider / routing chain
openclaw -> xiaomi
Additional provider/model setup details
I went straight to the Xiaomi website, took out an API key there and gave it to OpenClaw to process (which at that time ran under Claude Opus 4.7).
Logs, screenshots, and evidence
Here are some excerpts of the log file:
Config warnings:
- plugins.entries.brave: plugin not installed: brave — install the official external plugin with: openclaw plugins install @openclaw/brave-plugin
🦞 OpenClaw 2026.5.12 (f066dd2) — Less clicking, more shipping, fewer "where did that file go" moments.
|
o
19:52:43 [gateway] loading configuration…
19:52:55 [gateway] resolving authentication…
19:52:55 [gateway] starting...
19:53:06 [gateway] starting HTTP server...
19:53:06 [health-monitor] started (interval: 300s, startup-grace: 60s, channel-connect-grace: 120s)
19:53:07 [gateway] agent model: xiaomi/mimo-v2.5-pro (thinking=medium, fast=off)
19:53:07 [gateway] http server listening (8 plugins: browser, canvas, device-pair, file-transfer, memory-core, memory-wiki, phone-control, talk-voice; 11.8s)
19:53:07 [gateway] log file: C:\Users\kurt_\AppData\Local\Temp\openclaw\openclaw-2026-05-15.log
19:53:08 [gateway] starting channels and sidecars...
19:53:08 [hooks] loaded 5 internal hook handlers
19:53:09 [browser/server] Browser control listening on http://127.0.0.1:18791/ (auth=token)
19:53:09 [gateway] ready
19:53:09 [heartbeat] started
19:53:18 [ws] protocol mismatch conn=1131ea2c-4866-421e-bf64-de9a871fce64 remote=127.0.0.1 client=openclaw-control-ui webchat vcontrol-ui
19:53:18 [ws] closed before connect conn=1131ea2c-4866-421e-bf64-de9a871fce64 peer=127.0.0.1:65022->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=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36 Edg/148.0.0.0 code=1002 reason=protocol mismatch
19:53:34 [ws] protocol mismatch conn=7f796e02-4414-42cc-b231-240a5a6b94c4 remote=127.0.0.1 client=openclaw-control-ui webchat vcontrol-ui
19:53:34 [ws] closed before connect conn=7f796e02-4414-42cc-b231-240a5a6b94c4 peer=127.0.0.1:65023->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=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36 Edg/148.0.0.0 code=1002 reason=protocol mismatch
19:53:50 [ws] protocol mismatch conn=2a4f628b-dd20-42d5-9915-cec17619a171 remote=127.0.0.1 client=openclaw-control-ui webchat vcontrol-ui
(this repeats several times)
20:01:12 [model-fallback/decision] model fallback decision: decision=candidate_failed requested=deepseek/deepseek-v4-flash candidate=deepseek/deepseek-v4-flash reason=timeout next=google/gemini-3.1-pro-preview detail=cron: isolated agent setup timed out before runner start
20:01:12 [model-fallback/decision] model fallback decision: decision=candidate_failed requested=deepseek/deepseek-v4-flash candidate=google/gemini-3.1-pro-preview reason=timeout next=deepseek/deepseek-v4-pro detail=cron: isolated agent setup timed out before runner start
20:01:12 [model-fallback/decision] model fallback decision: decision=candidate_failed requested=deepseek/deepseek-v4-flash candidate=deepseek/deepseek-v4-pro reason=timeout next=anthropic/claude-opus-4-6 detail=cron: isolated agent setup timed out before runner start
20:01:12 [model-fallback/decision] model fallback decision: decision=candidate_failed requested=deepseek/deepseek-v4-flash candidate=anthropic/claude-opus-4-6 reason=timeout next=google/gemini-3.1-flash-lite-preview detail=cron: isolated agent setup timed out before runner start
20:01:12 [model-fallback/decision] model fallback decision: decision=candidate_failed requested=deepseek/deepseek-v4-flash candidate=google/gemini-3.1-flash-lite-preview reason=timeout next=anthropic/claude-sonnet-4-6 detail=cron: isolated agent setup timed out before runner start
20:01:12 [model-fallback/decision] model fallback decision: decision=candidate_failed requested=deepseek/deepseek-v4-flash candidate=anthropic/claude-sonnet-4-6 reason=timeout next=google/gemini-3-flash-preview detail=cron: isolated agent setup timed out before runner start
20:01:12 [model-fallback/decision] model fallback decision: decision=candidate_failed requested=deepseek/deepseek-v4-flash candidate=google/gemini-3-flash-preview reason=timeout next=none detail=cron: isolated agent setup timed out before runner start
20:01:13 [ws] protocol mismatch conn=4368308f-c071-4626-96c8-afd73d0fcf65 remote=127.0.0.1 client=openclaw-control-ui webchat vcontrol-ui
20:01:13 [ws] closed before connect conn=4368308f-c071-4626-96c8-afd73d0fcf65 peer=127.0.0.1:65068->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=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36 Edg/148.0.0.0 code=1002 reason=protocol mismatch
(again repeating several times)
Impact and severity
Affected: Users on Windows 10 using OpenClaw directly via the gateway
Severity: blocks workflow completely
Frequency: always
Consequence: can't use OpenClaw at all
Additional information
Last known good version: 2026.5.x (can't remember exactly, I think x=2 or 6)
Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
After upgrading OpenClaw to Version 2026.5.12, the gateway became unusable for me. I had left the browser open, but instead of reconnecting to the gateway, it just reported a "protocol mismatch". So I again pointed the browser (MS Edge) at the address given on top of the output in the command window, "http://127.0.0.1:18791/", but it just shows the word "Unauthorized". The logfile itself reports a "protocol mismatch", later all used models time out.
System data:
Operating system: Windows 10
Browser: MS Edge
Default model: xiaomi/mimo-v2.5-pro
Steps to reproduce
Expected behavior
Normally, the Gateway should start up, and after at most 1-2 minutes, the chat window should appear with the agent ready to accept commands or discussions.
Actual behavior
The Gateway only shows the word "Unauthorized".
OpenClaw version
2026.5.12
Operating system
Windows 10
Install method
npm
Model
xiaomi/mimo-v2.5-pro
Provider / routing chain
openclaw -> xiaomi
Additional provider/model setup details
I went straight to the Xiaomi website, took out an API key there and gave it to OpenClaw to process (which at that time ran under Claude Opus 4.7).
Logs, screenshots, and evidence
Impact and severity
Affected: Users on Windows 10 using OpenClaw directly via the gateway
Severity: blocks workflow completely
Frequency: always
Consequence: can't use OpenClaw at all
Additional information
Last known good version: 2026.5.x (can't remember exactly, I think x=2 or 6)