#Hi! I'm having an issue with the web panel.

1 messages · Page 1 of 1 (latest)

fierce totem
#

• Version: 2026.4.6 (Docker install on Hostinger VPS)
• Access: SSH tunnel, port 18789 → http://127.0.0.1:18789/?token=TOKEN
• Issue: Page loads (title shows "OpenClaw Control", favicon visible, dark background) but stays completely black.
• Console error: Uncaught ReferenceError: process is not defined
• openclaw doctor: All green, no errors.
• Tried: docker compose restart — issue persists.

Any idea what might be causing this? Thanks!

outer hearthBOT
#

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

oak roverBOT
#

Yep — that error (process is not defined) with a black Control UI usually means a broken/stale Control UI bundle, not a tunnel/auth issue.

Given your symptoms, this is very likely the same “Node-only code leaked into browser bundle” regression family.

Try this order:

  1. Rule out cached JS first
  • Open in incognito/private window
  • Hard refresh (Ctrl+Shift+R)
  • Clear site data for 127.0.0.1:18789
  1. Make sure you’re not on a bad floating image
  • Check your image tag (main can be unstable)
  • Re-pull + recreate containers:
docker compose pull
# 
docker compose up -d --force-recreate
  1. Confirm the runtime version from inside the container
docker compose run --rm openclaw-cli openclaw --version

If it still stays black, paste:

  • first red stack trace line from browser console (with the index-*.js filename),
  • output of the version command above,
  • and I’ll pinpoint whether it’s a known 2026.4.6 bundle regression.

Docs: https://docs.openclaw.ai/install/docker · https://docs.openclaw.ai/web/control-ui · https://docs.openclaw.ai/gateway/troubleshooting#dashboard-control-ui-connectivity

fierce totem
#

It stills black yes

#

OpenClaw 2026.4.6 is the version

oak roverBOT
#

Perfect, that stack line confirms it — this is not your SSH tunnel/auth setup.

index-Bbm8PjcN.js + ReferenceError: process is not defined is the same Control UI bundle regression family (Node-only code leaking into browser JS).

What to do now

  1. Force-refresh both sides (browser + image)
docker compose pull
docker compose up -d --force-recreate

Then clear site data for 127.0.0.1:18789 (or test in private/incognito).

  1. If you’re on :main, switch to a pinned release tag
    Floating main images can carry this kind of UI regression.

  2. If still broken on 2026.4.6, treat it as a release bug

#

Got it — then this is almost certainly a 2026.4.6 Control UI regression, not your VPS/tunnel config.

Quick workaround: roll back one tag.

In docker-compose.yml, pin OpenClaw image(s) to:

image: ghcr.io/openclaw/openclaw:2026.4.5

Then redeploy:

docker compose pull
docker compose up -d --force-recreate

After that, open in a private window once (to avoid cached JS).

#

Yep — exactly. 2026.4.6 appears to be the broken one for this black-screen bug (process is not defined).

So the fix right now is to run a different tag (temporary rollback), e.g. 2026.4.5.

# docker-compose.yml
image: ghcr.io/openclaw/openclaw:2026.4.5

Then:

docker compose pull
docker compose up -d --force-recreate

If you want, paste your image: lines and I’ll tell you exactly what to change.

fierce axle
#

Had something similar on my Mac Mini setup — the "process is not defined" error is usually a browser environment issue where Node globals aren't available client-side.
Try a hard refresh first (Cmd+Shift+R) and if that doesn't work try a different browser entirely. Chrome vs Safari can behave differently with the token auth. Also worth checking if any browser extensions (ad blockers etc) are interfering with the panel loading.

oak roverBOT
#

Good call from PassiveBot on cache/extensions — worth a quick incognito test.

But with your exact combo (2026.4.6 + index-Bbm8PjcN.js + process is not defined) this is very likely a bad Control UI bundle in that release, not token auth or browser settings.

So if incognito still shows black:

  • roll back tag to 2026.4.5 (temporary workaround), or
  • wait for next patch and upgrade when released.

Tracking bug: https://github.com/openclaw/openclaw/issues/48176

fierce totem
#

Still black after --no-cache rebuild. First red stack trace:

Uncaught ReferenceError: process is not defined
at index-Bbm8PjcN.js:607

Version: 2026.4.6, image: openclaw:local (built locally)

oak roverBOT
#

Ah — image: openclaw:local is the key detail.

That means you’re running a locally built bundle, and your build is definitely shipping a broken Control UI asset (index-Bbm8PjcN.js), not a tunnel/browser problem.

Fastest path

Use an official image tag instead of local build for now:

image: ghcr.io/openclaw/openclaw:2026.4.5

Then:

docker compose pull
docker compose up -d --force-recreate