openclaw - 💡(How to fix) Fix v2026.3.31: Dashboard returns 500 Internal Server Error on GET / [18 comments, 15 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#58814Fetched 2026-04-08 02:32:26
View on GitHub
Comments
18
Participants
15
Timeline
21
Reactions
5

After updating to 2026.3.31, the dashboard at http://127.0.0.1:18789/ returns 500 Internal Server Error on every request. The gateway starts correctly (Telegram bots connect, WebSocket works, TUI works), but the HTTP handler crashes before serving any response.

Error Message

After updating to 2026.3.31, the dashboard at http://127.0.0.1:18789/ returns 500 Internal Server Error on every request. The gateway starts correctly (Telegram bots connect, WebSocket works, TUI works), but the HTTP handler crashes before serving any response. 3. curl http://127.0.0.1:18789/ returns 500 Internal Server Error

  • Nothing is logged for the 500 — error happens before logger kicks in

Root Cause

After updating to 2026.3.31, the dashboard at http://127.0.0.1:18789/ returns 500 Internal Server Error on every request. The gateway starts correctly (Telegram bots connect, WebSocket works, TUI works), but the HTTP handler crashes before serving any response.

RAW_BUFFERClick to expand / collapse

Bug Report

Version: 2026.3.31 (213a704) Install method: Homebrew + npm reinstall with --ignore-scripts OS: macOS (arm64)

Description

After updating to 2026.3.31, the dashboard at http://127.0.0.1:18789/ returns 500 Internal Server Error on every request. The gateway starts correctly (Telegram bots connect, WebSocket works, TUI works), but the HTTP handler crashes before serving any response.

Steps to Reproduce

  1. Install [email protected] via homebrew or npm install -g [email protected] --ignore-scripts
  2. Run openclaw gateway start
  3. curl http://127.0.0.1:18789/ returns 500 Internal Server Error

What Works

  • Gateway starts successfully
  • Telegram bots connect and respond
  • TUI works, WebSocket works

What Does Not Work

  • GET / returns 500
  • GET /openclaw/ returns 500
  • Dashboard URL with token returns 500

Notes

  • dist/control-ui/index.html EXISTS at the correct path
  • Nothing is logged for the 500 — error happens before logger kicks in
  • --ignore-scripts was required due to [email protected] native build failure (node-addon-api missing)
  • Had to manually install missing deps: grammy, @grammyjs/runner, @grammyjs/transformer-throttler, @buape/carbon

extent analysis

TL;DR

The 500 Internal Server Error on the dashboard at http://127.0.0.1:18789/ may be related to issues with the HTTP handler or missing dependencies, and verifying the installation and dependencies of [email protected] could help resolve the issue.

Guidance

  • Verify that all dependencies, including grammy, @grammyjs/runner, @grammyjs/transformer-throttler, and @buape/carbon, are correctly installed and up-to-date.
  • Check the installation of [email protected] and ensure that node-addon-api is available, as the --ignore-scripts flag may have skipped important installation steps.
  • Confirm that dist/control-ui/index.html is correctly served by the HTTP handler and that there are no issues with file system permissions or access.
  • Consider reinstalling [email protected] without the --ignore-scripts flag to ensure that all scripts are executed correctly.

Example

No code snippet is provided as the issue does not specify a particular code-related problem.

Notes

The issue may be related to the use of the --ignore-scripts flag during installation, which could have skipped important setup or configuration steps. Additionally, the missing dependencies and [email protected] native build failure may be contributing factors.

Recommendation

Apply workaround: Reinstall [email protected] without the --ignore-scripts flag and ensure that all dependencies are correctly installed and up-to-date, as this may resolve the issues with the HTTP handler and missing dependencies.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING