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.]
Set up an auth WebUI using git-8d257ed. Start up with a bind mount for data.
Log in, create users with the admin panel.
Update the image to the current main or git-13b0e7d.
Try to log in again.
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!
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:
```bash
docker run -d \
-p 3000:8080 \
--add-host=host.docker.internal:host-gateway \
-v /home/danny/ai/webui-settings:/app/backend/data \
-e WEBUI_AUTH=True \
--name open-webui \
--restart always ghcr.io/open-webui/open-webui:main
```
- works: git-8d257ed
- doesn't: git-13b0e7d
## Environment
- **Open WebUI Version:** - git-8d257ed (docker images are tagged main, latest and git, but not webui versions) - 0.3.13.
- **Operating System:** [e.g., Windows 10, macOS Big Sur, Ubuntu 20.04] - Docker
- **Browser (if applicable):** [e.g., Chrome 100.0, Firefox 98.0] - All
**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.
- [ ] I have included the browser console logs.
- [ ] I have included the Docker container logs.
- [x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
## 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.]
- Set up an auth WebUI using git-8d257ed. Start up with a bind mount for data.
- Log in, create users with the admin panel.
- Update the image to the current main or git-13b0e7d.
- Try to log in again.
## 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!
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 @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!