Originally created by @hkng on GitHub (May 9, 2024).
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:
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).
# 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:**

**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
There were some post-release hotfixes for SSO sign-in issues, please try re-pulling the image and re-running your container.
@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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @hkng on GitHub (May 9, 2024).
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:
Logs and Screenshots
Browser Console Logs:

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
@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.