github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-31 22:08:51 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

Issue: Unable to log in after updating the container without changing the password #5396

New Issue
Closed
opened 2025-11-11 16:19:52 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-11 16:19:52 -06:00
Owner
Copy Link

Originally created by @Adsryen on GitHub (May 30, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

maybe v0.6.13 Anyway, it's the latest

Ollama Version (if applicable)

No response

Operating System

centos7

Browser (if applicable)

edge

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

Unable to log in after updating the container without changing the password

Image

Actual Behavior

I am trying to reset it
Image

But it has no effect, including restarting the container

Steps to Reproduce

  1. Normal operation of the previous version
  2. Executed Docker Pull to pull the latest main image from the Docker Compose file directory
  3. Started and stopped the yml file, waiting for it to run again
  4. There was no password change operation throughout the entire process
  5. After running again, log in to the administrator and receive a prompt: The email or password provided is incorrect. Please check for typos and try logging in again.

Logs & Screenshots

2025-05-30 01:20:23.066 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 118.112.75.44:0 - "GET /static/favicon-dark.png HTTP/1.1" 200 - {}
2025-05-30 01:20:26.153 | INFO | open_webui.models.auths:authenticate_user:131 - authenticate_user: 159@qq.com - {}
2025-05-30 01:20:26.165 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 118.112.75.44:0 - "POST /api/v1/auths/signin HTTP/1.1" 400 - {}
2025-05-30 01:20:31.892 | INFO | open_webui.models.auths:authenticate_user:131 - authenticate_user: 159@qq.com - {}
2025-05-30 01:20:31.898 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 118.112.75.44:0 - "POST /api/v1/auths/signin HTTP/1.1" 400 - {}
2025-05-30 01:20:33.152 | INFO | open_webui.models.auths:authenticate_user:131 - authenticate_user: 159@qq.com - {}
2025-05-30 01:20:33.157 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 118.112.75.44:0 - "POST /api/v1/auths/signin HTTP/1.1" 400 - {}
2025-05-30 01:20:46.124 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 85.113.70.241:0 - "GET / HTTP/1.1" 200 - {}
2025-05-30 01:20:46.182 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 103.244.88.48:0 - "GET / HTTP/1.1" 200 - {}

Additional Information

No response

Originally created by @Adsryen on GitHub (May 30, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version maybe v0.6.13 Anyway, it's the latest ### Ollama Version (if applicable) _No response_ ### Operating System centos7 ### Browser (if applicable) edge ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior Unable to log in after updating the container without changing the password ![Image](https://github.com/user-attachments/assets/bb46d153-43ca-40e9-a9d7-1c15a8a2e91c) ### Actual Behavior I am trying to reset it ![Image](https://github.com/user-attachments/assets/25e6f32f-ea87-4ac6-a7e4-fdabee221330) But it has no effect, including restarting the container ### Steps to Reproduce 1. Normal operation of the previous version 2. Executed Docker Pull to pull the latest main image from the Docker Compose file directory 3. Started and stopped the yml file, waiting for it to run again 4. There was no password change operation throughout the entire process 5. After running again, log in to the administrator and receive a prompt: The email or password provided is incorrect. Please check for typos and try logging in again. ### Logs & Screenshots 2025-05-30 01:20:23.066 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 118.112.75.44:0 - "GET /static/favicon-dark.png HTTP/1.1" 200 - {} 2025-05-30 01:20:26.153 | INFO | open_webui.models.auths:authenticate_user:131 - authenticate_user: 159@qq.com - {} 2025-05-30 01:20:26.165 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 118.112.75.44:0 - "POST /api/v1/auths/signin HTTP/1.1" 400 - {} 2025-05-30 01:20:31.892 | INFO | open_webui.models.auths:authenticate_user:131 - authenticate_user: 159@qq.com - {} 2025-05-30 01:20:31.898 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 118.112.75.44:0 - "POST /api/v1/auths/signin HTTP/1.1" 400 - {} 2025-05-30 01:20:33.152 | INFO | open_webui.models.auths:authenticate_user:131 - authenticate_user: 159@qq.com - {} 2025-05-30 01:20:33.157 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 118.112.75.44:0 - "POST /api/v1/auths/signin HTTP/1.1" 400 - {} 2025-05-30 01:20:46.124 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 85.113.70.241:0 - "GET / HTTP/1.1" 200 - {} 2025-05-30 01:20:46.182 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 103.244.88.48:0 - "GET / HTTP/1.1" 200 - {} ### Additional Information _No response_
GiteaMirror added the bug label 2025-11-11 16:19:52 -06:00
GiteaMirror commented 2025-11-11 16:19:53 -06:00
Author
Owner
Copy Link

@Adsryen commented on GitHub (May 30, 2025):

use
Image

Successfully changed password, of course, pay attention to escaping special characters

But updating the container should not cause my account password to become invalid, which may still be a bug

@Adsryen commented on GitHub (May 30, 2025): use ![Image]( https://github.com/user-attachments/assets/25e6f32f-ea87-4ac6-a7e4-fdabee221330 ) Successfully changed password, of course, pay attention to escaping special characters But updating the container should not cause my account password to become invalid, which may still be a bug
GiteaMirror commented 2025-11-11 16:19:53 -06:00
Author
Owner
Copy Link

@rgaricano commented on GitHub (May 30, 2025):

This happens to me sometimes when updating, I fix it by clearing cookies, reloading and retyping user & pass.

@rgaricano commented on GitHub (May 30, 2025): This happens to me sometimes when updating, I fix it by clearing cookies, reloading and retyping user & pass.
GiteaMirror commented 2025-11-11 16:19:53 -06:00
Author
Owner
Copy Link

@dexogen commented on GitHub (May 30, 2025):

Same issue here - after today’s update, my password doesn’t work anymore, even when I try resetting it like they say. Clearing cookies and any other storage doesn’t help either.

@dexogen commented on GitHub (May 30, 2025): Same issue here - after today’s update, my password doesn’t work anymore, even when I try resetting it like they say. Clearing cookies and any other storage doesn’t help either.
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 bug
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#5396
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?