openclaw - 💡(How to fix) Fix [Bug]: Gateway token mismatch prevents connection between Control UI and Gateway [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#72203Fetched 2026-04-27 05:33:22
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Participants
Timeline (top)
labeled ×1

Control UI cannot connect to the local Gateway due to a gateway token mismatch error immediately after setup.

Error Message

Control UI cannot connect to the local Gateway due to a gateway token mismatch error immediately after setup. Observe health check failure with token mismatch error.

Root Cause

Control UI cannot connect to the local Gateway due to a gateway token mismatch error immediately after setup.

Code Example

Relevant output during setup:

Health check failed: unauthorized: gateway token mismatch (provide gateway auth token)

Control UI state:

Gateway: not detected (unauthorized: gateway token mismatch (provide gateway auth token))

Gateway details:

Web UI: http://127.0.0.1:18789/
Gateway WS: ws://127.0.0.1:18789
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Control UI cannot connect to the local Gateway due to a gateway token mismatch error immediately after setup.

Steps to reproduce

Run openclaw and complete QuickStart setup with default options (Gateway auth: Token). Wait for Gateway service installation to complete. Observe health check failure with token mismatch error. Run openclaw dashboard. Open the provided Web UI URL. Observe that Gateway is “not detected” in the Control UI.

Expected behavior

After setup, the Control UI connects to the local Gateway using the configured token and the Gateway is detected as healthy.

Actual behavior

The Gateway fails health check with: unauthorized: gateway token mismatch (provide gateway auth token)

The Control UI shows: Gateway: not detected (unauthorized: gateway token mismatch (provide gateway auth token))

OpenClaw version

OpenClaw 2026.4.24 (cbcfdf6)

Operating system

Ubuntu 25.04

Install method

curl -fsSL https://openclaw.ai/install.sh | bash

Model

Openai

Provider / routing chain

Openai

Additional provider/model setup details

<img width="926" height="963" alt="Image" src="https://github.com/user-attachments/assets/560ffbb0-5a9c-4724-b5ce-0690f72447c1" />

Logs, screenshots, and evidence

Relevant output during setup:

Health check failed: unauthorized: gateway token mismatch (provide gateway auth token)

Control UI state:

Gateway: not detected (unauthorized: gateway token mismatch (provide gateway auth token))

Gateway details:

Web UI: http://127.0.0.1:18789/
Gateway WS: ws://127.0.0.1:18789

Impact and severity

SEVERE Affected users: users performing initial setup with default configuration Severity: blocks workflow Frequency: always (observed during initial setup) Consequence: prevents connection between Control UI and Gateway, blocking usage

Additional information

No response

extent analysis

TL;DR

The most likely fix is to reconfigure the Gateway token in the Control UI to match the one expected by the Gateway service.

Guidance

  • Verify the Gateway token configured during the QuickStart setup matches the one expected by the Gateway service.
  • Check the Gateway service installation logs for any errors or warnings related to token configuration.
  • Attempt to manually set the Gateway token in the Control UI to the expected value and observe if the health check passes.
  • Review the OpenClaw documentation for any specific requirements or constraints on Gateway token configuration.

Example

No code snippet is provided as the issue is related to configuration and token mismatch.

Notes

The provided information suggests a configuration issue rather than a code problem, so the focus should be on verifying and correcting the Gateway token configuration.

Recommendation

Apply workaround: manually configure the correct Gateway token in the Control UI, as the issue seems to be related to a token mismatch error, and reconfiguring the token might resolve the connection issue between the Control UI and the Gateway.

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

After setup, the Control UI connects to the local Gateway using the configured token and the Gateway is detected as healthy.

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]: Gateway token mismatch prevents connection between Control UI and Gateway [1 participants]