mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 19:08:59 -05:00
issue: Can't login after reinstalling open-webui and recovering db #6227
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 @philippmkoch on GitHub (Aug 27, 2025).
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.6.25
Ollama Version (if applicable)
No response
Operating System
macOS 15.6.1
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Successful login with admin-account
Actual Behavior
I am experiencing a critical issue with Open WebUI (0.6.25). Initially, the application crashed unexpectedly. After restarting the docker container, I was unable to access the backend. I then proceeded to reinstall Open WebUI using Docker (docker-compose) with Docker Desktop (4.44.3 (202357) on my Mac (macOS 15.6.1), but this did not resolve the issue.
Following the unsuccessful reinstallation, I recovered all data and the database via Time Machine. Unfortunately, this also did not solve the problem. Currently, I can see the login screen, but I am unable to log in.
I am now receiving the following error:
'The email or password provided is incorrect. Please check for typos and try logging in again.'
Steps to Reproduce
Logs & Screenshots
Additionally, I see the following data in the docker-desktop-logs:
2025-08-26 22:59:49.595 | INFO | open_webui.models.auths:authenticate_user:126 - authenticate_user: xxxxxx@xxxxxx.xxx
2025-08-26 22:59:49.597 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - xxx.xx.xx.xx:x - "POST /api/v1/auths/signin HTTP/1.1" 40
Additional Information
I also tried to log in with a normal user-account and I'm getting the same error, and in this instance, the authenticate_user in the logs is the same as if I try to log in with the admin-account. I also tried to change the password as mentioned in the troubleshooting details but without any success.