Protocol Missmatch on gateway using ssh

[echo cape]

I use this in a .bat to start it and i am getting protocol missmatch after updating

echo Starting SSH tunnel to %USER%@%HOST% ...
start "OpenClaw SSH Tunnel" cmd /k ssh -N -L %LOCAL_PORT%:127.0.0.1:%REMOTE_PORT% %USER%@%HOST%

timeout /t 2 >nul
start "" "http://127.0.0.1:%LOCAL_PORT%/#token=%TOKEN%"
echo.
echo Tunnel started in a separate window.
echo Keep that window open while using OpenClaw.

[dim mortar]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[vocal vapor]

Prosky, that .bat tunnel pattern is basically fine as long as %LOCAL_PORT% forwards to the gateway’s actual remote port, usually 18789.

“protocol mismatch” usually means the browser/client UI and the running Gateway are from different OpenClaw builds after the update. First thing: can you run this on the gateway host and share the output?

openclaw --version
openclaw status
openclaw gateway status

Then try the repair path on the gateway host:

openclaw doctor
openclaw gateway restart

[vocal vapor]

If you installed/running from source, also rebuild the Control UI from the repo checkout:

pnpm install
pnpm build
pnpm ui:build
openclaw gateway restart

After that, reopen the tunnel and hard-refresh the browser tab. If it still fails, open a fresh/private browser window at:

http://127.0.0.1:%LOCAL_PORT%/#token=%TOKEN%

Docs for the relevant bits:
https://docs.openclaw.ai/help/faq