mirror of
https://github.com/open-webui/open-webui.git
synced 2026-03-25 04:24:30 -05:00
Auth broken in most recent docker image #1811
Reference in New Issue
Block a user
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?
Originally created by @dannystaple on GitHub (Aug 18, 2024).
Bug Report
Installation Method
[Describe the method you used to install the project, e.g., git clone, Docker, pip, etc.]
Installation using docker, with the following script:
Environment
Confirmation:
Expected Behavior:
[Describe what you expected to happen.]
Auth continues to work in the Latest/main docker image.
Actual Behavior:
[Describe what actually happened.]
In docker image created 4 days ago - tagged git-13b0e7d, created in job https://github.com/open-webui/open-webui/actions/runs/10393992869, auth no longer works, all users are unable to autheticate.
Description
Bug Summary:
[Provide a brief but clear summary of the bug]
User authentication breaks, every user is told incorrect credentials, after starting WebUI with an existing set of data, but this newer image. Resetting to the previous docker image tag works.
Reproduction Details
Steps to Reproduce:
[Outline the steps to reproduce the bug. Be as detailed as possible.]
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Logging doesn't show anything.
Screenshots/Screen Recordings (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!