Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Control UI assets missing in NPM release 2026.3.22 [6 comments, 6 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#52848•Fetched 2026-04-08 01:18:34
View on GitHub
Comments
6
Participants
6
Timeline
11
Reactions
2
Author
FirdhanAlamsyahFirdhanAlamsyah
Participants
dao-666dao-666FirdhanAlamsyahFirdhanAlamsyahGuaiYiHuGuaiYiHukevinheinrichskevinheinrichsslideshow-dingoslideshow-dingosteipetesteipete
Timeline (top)
commented ×6labeled ×2closed ×1locked ×1

Hi team! I just updated my global OpenClaw installation from 2026.3.13 to the latest version (2026.3.22), and the Gateway Dashboard (Control UI) completely broke. Instead of loading the UI, accessing the gateway URL via browser returns a 503 Service Unavailable with a plaintext error.

Error Message

Hi team! I just updated my global OpenClaw installation from 2026.3.13 to the latest version (2026.3.22), and the Gateway Dashboard (Control UI) completely broke. Instead of loading the UI, accessing the gateway URL via browser returns a 503 Service Unavailable with a plaintext error. 4. See the plaintext error message instead of the login/pairing screen.

Root Cause

Root Cause Analysis: I inspected the actual NPM package tarball for [email protected] and compared it to 2026.3.13. It seems that the dist/control-ui/ directory was completely omitted from the published 2026.3.22 NPM package (likely an issue during the CI/CD build step, .npmignore, or the files array in package.json).

Fix Action

Fix / Workaround

Hope this helps patch it quickly! Let me know if you need any more details.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

Hi team! I just updated my global OpenClaw installation from 2026.3.13 to the latest version (2026.3.22), and the Gateway Dashboard (Control UI) completely broke. Instead of loading the UI, accessing the gateway URL via browser returns a 503 Service Unavailable with a plaintext error.

Steps to reproduce

  1. Run npm install -g [email protected] on a Linux VPS.
  2. Start the gateway using openclaw gateway start.
  3. Open the Gateway URL (e.g., http://127.0.0.1:18789 or via Tailscale Serve) in a browser.
  4. See the plaintext error message instead of the login/pairing screen.

Expected behavior

log in to dashboard

Actual behavior

Control UI assets not found. Build them with pnpm ui:build (auto-installs UI deps), or run pnpm ui:dev during development.

OpenClaw version

v2026.3.22

Operating system

Ubuntu 24.04

Install method

No response

Model

gemini 3.1

Provider / routing chain

openclaw - gateway - gemini ai

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

Root Cause Analysis: I inspected the actual NPM package tarball for [email protected] and compared it to 2026.3.13. It seems that the dist/control-ui/ directory was completely omitted from the published 2026.3.22 NPM package (likely an issue during the CI/CD build step, .npmignore, or the files array in package.json).

Downgrading back to [email protected] fixes the issue immediately since the dist/control-ui/index.html and its assets are present in that tarball.

Hope this helps patch it quickly! Let me know if you need any more details.

extent analysis

Fix Plan

To resolve the issue, we need to ensure the dist/control-ui/ directory is included in the published NPM package. Here are the steps:

  • Update the .npmignore file to exclude the dist/control-ui/ directory from being ignored.
  • Verify the files array in package.json includes the dist/control-ui/ directory.
  • Run the build command pnpm ui:build to generate the Control UI assets.
  • Re-publish the NPM package with the updated changes.

Example code changes:

// package.json
"files": [
  "dist/",
  "dist/control-ui/",
  // ... other files
],

// .npmignore
# Ignore unnecessary files
node_modules/
coverage/
// ... other ignored files

Alternatively, you can run pnpm ui:dev during development to build and serve the Control UI assets.

Verification

After applying the fix, verify that the Gateway Dashboard loads correctly by accessing the gateway URL in a browser. The login/pairing screen should be displayed instead of the plaintext error message.

Extra Tips

To prevent similar issues in the future, ensure that the CI/CD build step includes the necessary directories and files in the published NPM package. Regularly test the published package to catch any errors or omissions.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

log in to dashboard

#installation#permission error#memory optimization#batch processing#GPU compatibility

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Control UI assets missing in NPM release 2026.3.22 [6 comments, 6 participants]