#ASAP

1 messages · Page 1 of 1 (latest)

loud patio
#

the new update kill the web UI.. what happen its what i use to talk to the agents

faint moonBOT
#

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

frigid citrusBOT
#

Yep — that usually means the gateway/auth handshake got out of sync after update (or UI assets weren’t rebuilt on source installs).

Run these and paste the outputs:

openclaw --version
openclaw gateway status
openclaw status --all
openclaw dashboard

If dashboard opens but says unauthorized/reconnecting, grab token and paste it in Control UI → Gateway Access:

openclaw config get gateway.auth.token
loud patio
#

every new update something break

frigid citrusBOT
#

Yeah, that frustration is totally fair. If each update breaks your UI, we should treat it like a repeatable upgrade bug and pin it down once.

Can you paste these 3 outputs so I can give you an exact fix (not guesswork)?

openclaw --version
openclaw gateway status
openclaw doctor

Also tell me the UI symptom:

  • blank page
  • unauthorized loop
  • “disconnected from gateway”
  • won’t load at all

If you want max stability while we debug, stick to stable channel only:

royal jetty
#

I got this error too. are you fixed it?

frigid citrusBOT
#

For one person in this thread, yes — theirs was fixed. Root cause was:

  1. invalid BlueBubbles config keys (host / port) crashing startup
  2. gateway token mismatch between env and config

If you want, paste your exact error text and I can tell in 1–2 messages if it’s the same issue.

Quick checks first:

openclaw --version
openclaw gateway status
openclaw logs --follow

If you’re using BlueBubbles and logs mention unknown keys, remove those invalid keys and restart gateway.