Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Custom avatar image returns 401 Unauthorized in Control UI after v2026.4.23 update [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#71551•Fetched 2026-04-26 05:11:36
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
wangzihe843-hashwangzihe843-hash
Participants
steipetesteipetewangzihe843-hashwangzihe843-hash
Timeline (top)
closed ×1commented ×1subscribed ×1

Custom avatar image set via IDENTITY.md returns HTTP 401 Unauthorized in Control UI after updating from v2026.4.21 to v2026.4.23.

Error Message

  • The 401 error is from OpenClaw's own static file serving, not an external resource

Root Cause

Possible root cause

v2026.4.22 or v2026.4.23 may have changed how static workspace files (including avatars) are served in the Control UI, possibly adding authentication checks that did not exist in v2026.4.21. The 401 suggests the Control UI's static file handler now requires authentication for workspace assets that were previously served anonymously.

Fix Action

Fix / Workaround

Workarounds attempted

  1. Verified the image file exists at the correct path
  2. Verified IDENTITY.md configuration is correct
  3. Verified workspace path in openclaw.json is correct
  4. Rolling back to v2026.4.21 is the only confirmed workaround
RAW_BUFFERClick to expand / collapse

Bug type

Control UI / avatar rendering

Beta release blocker

No

Summary

Custom avatar image set via IDENTITY.md returns HTTP 401 Unauthorized in Control UI after updating from v2026.4.21 to v2026.4.23.

Steps to reproduce

  1. Set a custom avatar image path in IDENTITY.md (e.g. Avatar: avatars/95bcc467d30eb08f6c9b245e48a48035.png)
  2. Place the image file in the workspace directory (e.g. D:.openclaw\workspace\avatars)
  3. Update OpenClaw from v2026.4.21 to v2026.4.23
  4. Open Control UI at http://127.0.0.1:18789
  5. Observe browser console: Failed to load resource: the server responded with a status of 401 (Unauthorized)

Expected behavior

The custom avatar image should be displayed in the Control UI chat interface, as it was before the update.

Actual behavior

  • Browser console shows: Failed to load resource: the server responded with a status of 401 (Unauthorized)
  • The avatar falls back to the default lobster emoji
  • The image file exists at the correct path and is referenced correctly in IDENTITY.md
  • The same configuration works correctly on v2026.4.21

OpenClaw version

v2026.4.23 (updated from v2026.4.21)

Operating system

Windows 11 (x64)

Install method

npm global install

Model

MiniMax-M2.7-highspeed (Token Plan)

Additional context

  • Avatar path in IDENTITY.md: Avatar: avatars/95bcc467d30eb08f6c9b245e48a48035.png
  • Image file confirmed to exist at: D:/.openclaw/workspace/avatars/95bcc467d30eb08f6c9b245e48a48035.png
  • Workspace path in openclaw.json: D:/.openclaw/workspace
  • No changes were made to IDENTITY.md or the avatar file between updating and observing the bug
  • The 401 error is from OpenClaw's own static file serving, not an external resource

Workarounds attempted

  1. Verified the image file exists at the correct path
  2. Verified IDENTITY.md configuration is correct
  3. Verified workspace path in openclaw.json is correct
  4. Rolling back to v2026.4.21 is the only confirmed workaround

Possible root cause

v2026.4.22 or v2026.4.23 may have changed how static workspace files (including avatars) are served in the Control UI, possibly adding authentication checks that did not exist in v2026.4.21. The 401 suggests the Control UI's static file handler now requires authentication for workspace assets that were previously served anonymously.

extent analysis

TL;DR

The most likely fix is to configure or disable the new authentication checks for static workspace files introduced in v2026.4.22 or v2026.4.23.

Guidance

  • Verify the authentication settings for static file serving in the Control UI to see if there are any changes or new requirements compared to v2026.4.21.
  • Check the release notes for v2026.4.22 and v2026.4.23 to confirm if there were changes to how static files are served and if any new configuration options were added.
  • Consider temporarily disabling any new authentication checks for static files to test if this resolves the issue, while also evaluating the security implications of such a change.
  • Review the OpenClaw documentation for any updates on serving custom avatars and authentication requirements.

Example

No specific code example can be provided without more details on the authentication mechanism introduced in the updates.

Notes

The exact solution depends on understanding the changes made in v2026.4.22 and v2026.4.23 regarding static file serving and authentication. Without access to the specific code changes or detailed release notes, the best approach is to investigate the authentication settings and release notes.

Recommendation

Apply a workaround by potentially disabling new authentication checks for static files if such an option is available, as rolling back to v2026.4.21 is confirmed to work but may not be a long-term solution.

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

The custom avatar image should be displayed in the Control UI chat interface, as it was before the update.

#inference speed#output truncation#response parsing#generation error#database connection

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]: Custom avatar image returns 401 Unauthorized in Control UI after v2026.4.23 update [1 comments, 2 participants]