openclaw - 💡(How to fix) Fix [Bug]: Control UI sends null client.id/client.mode through Cloudflare tunnel [1 comments, 2 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#78674Fetched 2026-05-07 03:33:59
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
2
Author
Timeline (top)
commented ×1mentioned ×1subscribed ×1

Error Message

Summary: Control UI sends null client.id and client.mode in WebSocket connect frame when loaded through a Cloudflare tunnel, causing a schema validation error. Manual WebSocket with identical params succeeds. Actual behavior: Connection fails with schema validation error. Gateway logs show origin=https://www.noahiberman.com but connect frame has no client fields populated.

  • Also tested with openclaw.noahiberman.com — same error

Code Example

"client":"openclaw-control-ui","mode":"webchat","version":"2026.5.4","platform":"Win32"

---

"origin":"https://www.noahiberman.com" ... "handshakeError":"invalid connect params: at /client/id: must be equal to one of the allowed values; at /client/mode: must be equal to one of the allowed values"
RAW_BUFFERClick to expand / collapse

Bug type: Bug

Summary: Control UI sends null client.id and client.mode in WebSocket connect frame when loaded through a Cloudflare tunnel, causing a schema validation error. Manual WebSocket with identical params succeeds.

Steps to reproduce:

  1. Install OpenClaw 2026.5.4 via npm on Windows 10
  2. Configure Cloudflare tunnel: agent.noahiberman.comhttp://localhost:18789
  3. Add https://agent.noahiberman.com to gateway.controlUi.allowedOrigins
  4. Open https://agent.noahiberman.com in browser
  5. Enter auth token and click Connect
  6. Observe "invalid connect params: at /client/id: must be equal to one of the allowed values; at /client/mode: must be equal to one of the allowed values"

Expected behavior: Control UI connects successfully, as it does at http://127.0.0.1:18789

Actual behavior: Connection fails with schema validation error. Gateway logs show origin=https://www.noahiberman.com but connect frame has no client fields populated.

Version: 2026.5.4

Operating system: Windows 10.0.19045

Install method: npm global

Logs and evidence:

Local success (127.0.0.1):

"client":"openclaw-control-ui","mode":"webchat","version":"2026.5.4","platform":"Win32"

Remote failure (agent.noahiberman.com):

"origin":"https://www.noahiberman.com" ... "handshakeError":"invalid connect params: at /client/id: must be equal to one of the allowed values; at /client/mode: must be equal to one of the allowed values"

Manual WebSocket test through tunnel succeeds with identical params.

Impact:

  • Severity: High (blocks all remote Control UI access through tunnels/proxies)
  • Frequency: Always
  • Consequence: Cannot access Control UI from any device except localhost

Additional info:

  • Also tested with openclaw.noahiberman.com — same error
  • Clearing browser cache, localStorage, service workers does not fix
  • Gateway auth token is correct
  • dangerouslyDisableDeviceAuth: true is set

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

openclaw - 💡(How to fix) Fix [Bug]: Control UI sends null client.id/client.mode through Cloudflare tunnel [1 comments, 2 participants]