Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug] HTTP 500 on all endpoints after upgrading to 2026.3.31 (WebSocket works fine) [1 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#59134•Fetched 2026-04-08 02:28:14
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Nerdless-ship-itNerdless-ship-it
Participants
Nerdless-ship-itNerdless-ship-it
Timeline (top)
closed ×1locked ×1

Error Message

After upgrading to 2026.3.31, all HTTP endpoints return 500 Internal Server Error:

Fix Action

Fix / Workaround

Steps to reproduce:

  1. Upgrade to 2026.3.31
  2. Run gateway as Scheduled Task service
  3. Try to open the dashboard in browser

Workaround: None found. Rolling back to 2026.3.28 resolves the HTTP endpoints.

Code Example

gateway already running under schtasks; waiting 5000ms before retrying startup
RAW_BUFFERClick to expand / collapse

Bug Description

Environment:

  • OS: Windows 10.0.26200 (x64)
  • Node: v24.14.0
  • OpenClaw: 2026.3.31 (npm package)
  • Gateway: running as Scheduled Task on port 18789

Issue: After upgrading to 2026.3.31, all HTTP endpoints return 500 Internal Server Error:

  • GET / → 500
  • GET /chat → 500
  • GET /openclaw/control-ui/ → 500
  • GET /openclaw/health → 500

WebSocket connections work fine (RPC calls via ws://127.0.0.1:18789 succeed). The Gateway itself is running and healthy — only the HTTP static file server / HTML renderer is broken.

Gateway logs show:

gateway already running under schtasks; waiting 5000ms before retrying startup

(appears repeatedly, suggesting process supervisor confusion)

Expected behavior:

  • Dashboard at http://127.0.0.1:18789/ should load the Control UI HTML
  • /chat endpoint should return the chat interface

Actual behavior:

  • All HTTP endpoints return 500 with empty response body
  • Gateway RPC via WebSocket works correctly

Steps to reproduce:

  1. Upgrade to 2026.3.31
  2. Run gateway as Scheduled Task service
  3. Try to open the dashboard in browser

Workaround: None found. Rolling back to 2026.3.28 resolves the HTTP endpoints.

Additional observations:

  • The gateway restart trigger (SIGUSR1) fires multiple times causing multiple processes to attempt startup
  • Config version and running binary version mismatch may contribute
  • All plugins load correctly including memory-lancedb-pro (35 entries backed up successfully)
  • WebSocket RPC works perfectly, only HTTP serving layer is broken

Tags: http, gateway, windows, 2026.3.31

extent analysis

TL;DR

Downgrade to OpenClaw version 2026.3.28 to resolve the HTTP endpoint 500 Internal Server Error issue.

Guidance

  • Verify the gateway logs for any other errors or warnings that may indicate the root cause of the issue, in addition to the "gateway already running" message.
  • Check the config version and running binary version for any mismatches, as this may contribute to the problem.
  • Investigate the restart trigger (SIGUSR1) firing multiple times, as this could be causing multiple processes to attempt startup and leading to the error.
  • Test the HTTP endpoints with a tool like curl or Postman to see if the issue is specific to the browser or a more general problem.

Example

No code snippet is provided as the issue does not imply a specific code-related fix.

Notes

The issue seems to be specific to the 2026.3.31 version of OpenClaw, and downgrading to 2026.3.28 resolves the issue. However, this may not be a permanent solution, and further investigation is needed to determine the root cause.

Recommendation

Apply the workaround of downgrading to version 2026.3.28, as it is the only known solution at this time, and it resolves the HTTP endpoint issue.

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…
#authentication setup#request error#file not found#serialization error#model 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] HTTP 500 on all endpoints after upgrading to 2026.3.31 (WebSocket works fine) [1 participants]