#Getting Webchat UI errors.

1 messages · Page 1 of 1 (latest)

dire aurora
#

The Webchat UI is sending errors and the chat is experiencing glitches

control-ui-bootstrap.ts:29 GET http://127.0.0.1:18789/******************************/__openclaw/control-ui-config.json 404 (Not Found)
oh @ control-ui-bootstrap.ts:29
ah @ app-lifecycle.ts:45
connectedCallback @ app.ts:403
(anonymous) @ custom-element.js:6
w @ app-render.ts:1168
(anonymous) @ app.ts:111Understand this error
favicon.svg:1 GET http://127.0.0.1:18789/**************************/favicon.svg 404 (Not Found)
Image
j @ lit-html.js:6
_$AI @ lit-html.js:6
p @ lit-html.js:6
$ @ lit-html.js:6
_$AI @ lit-html.js:6
xu @ lit-html.js:6
update @ lit-element.js:6
performUpdate @ reactive-element.js:6
scheduleUpdate @ reactive-element.js:6
_$EP @ reactive-element.js:6
await in _$EP
requestUpdate @ reactive-element.js:6
_$Ev @ reactive-element.js:6
cn @ reactive-element.js:6
pn @ lit-element.js:6
x @ app.ts:116
(anonymous) @ custom-element.js:6
w @ app-render.ts:1168
(anonymous) @ app.ts:111Understand this error
favicon.svg:1 GET http://127.0.0.1:18789/***********************favicon.svg 404 (Not Found)Understand this error
favicon-32.png:1 GET http://127.0.0.1:18789/****************************
/favicon-32.png 404 (Not Found)

gray spruceBOT
#

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

lunar archBOT
#

Those 404s mean the Control UI is trying to load its “bootstrap config” and static assets from the wrong base path.

What’s happening

The UI always tries to fetch:

  • .../<basePath>/__openclaw/control-ui-config.json (bootstrap config)
  • .../<basePath>/favicon.svg, favicon-32.png (assets)

In your console the request is going to:

http://127.0.0.1:18789/***********/__openclaw/control-ui-config.json → 404

That usually happens when you opened the dashboard on a URL that has an extra path segment (that redacted ***********), e.g. something like:

http://127.0.0.1:18789/<something>/

…but your Gateway is serving the dashboard at the root (/), so /<something>/__openclaw/... doesn’t exist → 404 → UI gets half-initialized → “glitches”.

#

Fix

  1. Open the dashboard at exactly:
  • http://127.0.0.1:18789/ (no extra path segments)
  1. If it asks for auth, don’t put the token in the URL path.
    Paste your token into the Control UI auth field instead (Gateway Token / Password), then connect.

Token retrieval:

openclaw config get gateway.auth.token

Docs: https://docs.openclaw.ai/help/faq#how-do-i-authenticate-the-dashboard-token-on-localhost-vs-remote

Notes

  • The favicon 404s are mostly cosmetic, but they’re also a strong hint you’re on the wrong base path.
  • If you intentionally host the dashboard behind a reverse proxy under a subpath, then you must set gateway.controlUi.basePath to match that subpath and restart the gateway — otherwise you’ll keep getting exactly these 404s.
#

If you paste the full dashboard URL you’re opening (you can redact tokens), plus openclaw --version, I can tell you which of the two cases you’re in.

dire aurora
#

WORKED!!!