github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 06:03:26 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #2138] bug: Sign-in problem when WEBUI_AUTH_TRUSTED_EMAIL_HEADER is enabled #12769

New Issue
Closed
opened 2026-04-19 19:38:59 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-19 19:38:59 -05:00
Owner
Copy Link

Originally created by @hkng on GitHub (May 9, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/2138

Bug Report

Description

Sign-in problem after upgrade to v0.1.124 and WEBUI_AUTH_TRUSTED_EMAIL_HEADER is enabled

Bug Summary:

After upgrade to v0.1.124 and WEBUI_AUTH_TRUSTED_EMAIL_HEADER is set, error message detail "The email or password provided is incorrect. Please check for typos and try logging in again." popup. Examine the network traffic, it show bad request on /api/v1/signin

Steps to Reproduce:
upgrade to v0.1.124 and WEBUI_AUTH_TRUSTED_EMAIL_HEADER is enabled. No problem on v0.1.123

Expected Behavior:
Login sucessful

Actual Behavior:
[Describe what actually happened.]

Environment

  • **Open WebUI Version: v0.1.124

  • **Ollama (if applicable): any

  • **Operating System: Ubuntu 20.04

  • Browser (if applicable): Chrome 100.0

Reproduction Details

Confirmation:

  • I have read and followed all the instructions provided in the README.md.
  • I am on the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.

Logs and Screenshots

Browser Console Logs:
signin-problem

Docker Container Logs:
[Include relevant Docker container logs, if applicable]

Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]

Installation Method

Docker

Additional Information

Note

Originally created by @hkng on GitHub (May 9, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/2138 # Bug Report ## Description Sign-in problem after upgrade to v0.1.124 and WEBUI_AUTH_TRUSTED_EMAIL_HEADER is enabled **Bug Summary:** After upgrade to v0.1.124 and WEBUI_AUTH_TRUSTED_EMAIL_HEADER is set, error message detail "The email or password provided is incorrect. Please check for typos and try logging in again." popup. Examine the network traffic, it show bad request on /api/v1/signin **Steps to Reproduce:** upgrade to v0.1.124 and WEBUI_AUTH_TRUSTED_EMAIL_HEADER is enabled. No problem on v0.1.123 **Expected Behavior:** Login sucessful **Actual Behavior:** [Describe what actually happened.] ## Environment - **Open WebUI Version: v0.1.124 - **Ollama (if applicable): any - **Operating System: Ubuntu 20.04 - **Browser (if applicable):** Chrome 100.0 ## Reproduction Details **Confirmation:** - [x] I have read and followed all the instructions provided in the README.md. - [x] I am on the latest version of both Open WebUI and Ollama. - [x] I have included the browser console logs. - [ ] I have included the Docker container logs. ## Logs and Screenshots **Browser Console Logs:** ![signin-problem](https://github.com/open-webui/open-webui/assets/14144067/a76e5aa2-1d69-41e9-8056-d7d526a62689) **Docker Container Logs:** [Include relevant Docker container logs, if applicable] **Screenshots (if applicable):** [Attach any relevant screenshots to help illustrate the issue] ## Installation Method Docker ## Additional Information ## Note
GiteaMirror commented 2026-04-19 19:39:00 -05:00
Author
Owner
Copy Link

@justinh-rahb commented on GitHub (May 9, 2024):

There were some post-release hotfixes for SSO sign-in issues, please try re-pulling the image and re-running your container.

<!-- gh-comment-id:2102607768 --> @justinh-rahb commented on GitHub (May 9, 2024): There were some post-release hotfixes for SSO sign-in issues, please try re-pulling the image and re-running your container.
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#12769
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?