github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 02:48:13 -05:00
Code Issues 1.1k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #7485] UX: Unnecessary Misleading 401 Error and/or Re-login after updates #14764

New Issue
Closed
opened 2026-04-19 21:03:22 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-19 21:03:22 -05:00
Owner
Copy Link

Originally created by @TiancongLx on GitHub (Nov 30, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/7485

Description

After each update, users are experiencing two inconvenient behaviors:

  1. Forced re-authentication for all users
  2. Display of a misleading RED 401 error message

Current Behavior

  • Users are automatically logged out after updates
  • A RED 401 error message is displayed, suggesting an authentication error
  • This creates unnecessary anxiety for users, as no actual error has occurred

Expected Behavior

  • Preserve user sessions updates when possible
  • If re-authentication is absolutely necessary, show a friendly message explaining why
  • Remove the RED 401 error message and replace it with a more appropriate update notification

Impact

  • Degraded user experience
  • Unnecessary user anxiety due to error messages
  • Increased support inquiries about "errors" that aren't actual errors

One of my friends using my hosted OI daily, got confused for the red error.

"Did I do something wrong? Why?"
"There, there. It's just a normal new version release, and after a re-login it'll be OK. The 401 error code is meaning ..."

Technical Details

  • Affects all users regardless of their authentication status
  • Current implementation treats version changes as authentication failures

Proposed Solutions

  • Replace the error message with a user-friendly update notification
  • Add graceful session restoration logic
Originally created by @TiancongLx on GitHub (Nov 30, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/7485 ## Description After each update, users are experiencing two inconvenient behaviors: 1. Forced re-authentication for all users 2. Display of a misleading __RED__ 401 error message ## Current Behavior - Users are automatically logged out after updates - A __RED__ 401 error message is displayed, suggesting an authentication error - This creates unnecessary anxiety for users, as no actual error has occurred ## Expected Behavior - Preserve user sessions updates when possible - If re-authentication is absolutely necessary, show a friendly message explaining why - Remove the __RED__ 401 error message and replace it with a more appropriate update notification ## Impact - Degraded user experience - Unnecessary user anxiety due to error messages - Increased support inquiries about "errors" that aren't actual errors One of my friends using my hosted OI daily, got confused for the red error. > "Did I do something wrong? Why?" > "There, there. It's just a normal new version release, and after a re-login it'll be OK. The `401 error code` is meaning ..." ## Technical Details - Affects all users regardless of their authentication status - Current implementation treats version changes as authentication failures ## Proposed Solutions - Replace the error message with a user-friendly update notification - Add graceful session restoration logic
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#14764
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?