openclaw - 💡(How to fix) Fix [Bug]: Show QR button non-functional, control-ui-config.json returns 401 [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

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#77186Fetched 2026-05-05 05:51:17
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
2
Author
Timeline (top)
closed ×1commented ×1labeled ×1

Show QR button does not work in Control UI for WhatsApp channel linking. The /openclaw/control-ui-config.json endpoint returns 401 Unauthorized even with a valid dashboard token, breaking UI functionality.

Root Cause

Show QR button does not work in Control UI for WhatsApp channel linking. The /openclaw/control-ui-config.json endpoint returns 401 Unauthorized even with a valid dashboard token, breaking UI functionality.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Show QR button does not work in Control UI for WhatsApp channel linking. The /openclaw/control-ui-config.json endpoint returns 401 Unauthorized even with a valid dashboard token, breaking UI functionality.

Steps to reproduce

  1. Fresh install OpenClaw 2026.5.2 via npm on WSL2 / Ubuntu 24.04
  2. Install WhatsApp plugin: openclaw plugins install @openclaw/whatsapp
  3. Restart gateway: systemctl --user restart openclaw-gateway.service
  4. Run openclaw dashboard, open URL with token in browser
  5. Navigate to Channels → WhatsApp
  6. Click "Show QR"

Expected behavior

QR code appears for WhatsApp Web pairing.

Actual behavior

  • Show QR button does nothing
  • Browser console shows: Failed to load resource: the server responded with a status of 401 (Unauthorized) on /openclaw/control-ui-config.json
  • WhatsApp shows "not linked", no QR generated

OpenClaw version

OpenClaw version: 2026.5.2

Operating system

OS: Windows 11 + WSL2 (Ubuntu 24.04)

Install method

npm global

Model

anthropic/claude-sonnet-4-6

Provider / routing chain

openclaw -> anthropic/claude-sonnet-4-6

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

Affected: All WhatsApp channel users on OpenClaw 2026.5.2 (Control UI) Severity: High (blocks WhatsApp onboarding entirely) Frequency: Always — 100% reproducible across versions 2026.4.29 and 2026.5.2 Consequence: Cannot link WhatsApp account, no QR code generated, channel unusable

Additional information

  • Issue persists across version 2026.4.29 and 2026.5.2
  • Tried clearing ~/.openclaw/credentials/whatsapp and gateway restart
  • Tried Relink, Refresh, Wait for scan buttons — no QR generated
  • Telegram channel works fine on same install

extent analysis

TL;DR

The issue can be resolved by verifying the dashboard token validity and ensuring proper authentication for the /openclaw/control-ui-config.json endpoint.

Guidance

  • Verify that the dashboard token is correctly generated and passed to the /openclaw/control-ui-config.json endpoint.
  • Check the OpenClaw documentation for any specific authentication requirements for the Control UI.
  • Inspect the browser console for any additional error messages that may indicate the cause of the 401 Unauthorized response.
  • Consider testing the endpoint using a tool like curl to isolate the issue from the UI.

Example

No code example is provided as the issue is related to authentication and token validation, which requires specific knowledge of the OpenClaw API.

Notes

The issue may be related to a change in the authentication mechanism or token validation in OpenClaw version 2026.5.2. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Verify and regenerate the dashboard token to ensure proper authentication for the /openclaw/control-ui-config.json endpoint. This may resolve the issue temporarily until a permanent fix is available.

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

QR code appears for WhatsApp Web pairing.

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]: Show QR button non-functional, control-ui-config.json returns 401 [1 comments, 2 participants]