[GH-ISSUE #10205] After Watchtower Upgrade, "The email or password provided is incorrect " #135535

Closed
opened 2026-05-25 02:27:08 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @czar on GitHub (Feb 17, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/10205

Everything had been running smoothly for months, and I'd previously performed updates without issue. However, today I ran the upgrade to go from v0.5.10 to v0.5.12

docker run --rm --volume /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower --run-once open-webui

time="2025-02-17T18:34:27Z" level=info msg="Watchtower 1.7.1"
time="2025-02-17T18:34:27Z" level=info msg="Using no notifications"
time="2025-02-17T18:34:27Z" level=info msg="Only checking containers which name matches \"open-webui\""
time="2025-02-17T18:34:27Z" level=info msg="Running a one time update."
time="2025-02-17T18:36:12Z" level=info msg="Found new ghcr.io/open-webui/open-webui:main image (06e9c7ce6dbd)"
time="2025-02-17T18:36:12Z" level=info msg="Stopping /open-webui (c2bc4a9f17e8) with SIGTERM"
time="2025-02-17T18:36:17Z" level=info msg="Creating /open-webui"
time="2025-02-17T18:36:17Z" level=info msg="Session done" Failed=0 Scanned=1 Updated=1 notify=no
time="2025-02-17T18:36:17Z" level=info msg="Waiting for the notification goroutine to finish" notify=no

Then logged in with the primary admin account to find;

"The email or password provided is incorrect. Please check for typos and try logging in again."

I attempted alternative accounts and, as luck would have it, my backup account sufficed. However, I decided to take the precaution of changing the primary administrator's password and logging back in. It's worth noting that you should always ensure that you have a backup administrative account established – doing so can save considerable inconvenience in the long run.

Originally created by @czar on GitHub (Feb 17, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/10205 Everything had been running smoothly for months, and I'd previously performed updates without issue. However, today I ran the upgrade to go from v0.5.10 to v0.5.12 ``` docker run --rm --volume /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower --run-once open-webui time="2025-02-17T18:34:27Z" level=info msg="Watchtower 1.7.1" time="2025-02-17T18:34:27Z" level=info msg="Using no notifications" time="2025-02-17T18:34:27Z" level=info msg="Only checking containers which name matches \"open-webui\"" time="2025-02-17T18:34:27Z" level=info msg="Running a one time update." time="2025-02-17T18:36:12Z" level=info msg="Found new ghcr.io/open-webui/open-webui:main image (06e9c7ce6dbd)" time="2025-02-17T18:36:12Z" level=info msg="Stopping /open-webui (c2bc4a9f17e8) with SIGTERM" time="2025-02-17T18:36:17Z" level=info msg="Creating /open-webui" time="2025-02-17T18:36:17Z" level=info msg="Session done" Failed=0 Scanned=1 Updated=1 notify=no time="2025-02-17T18:36:17Z" level=info msg="Waiting for the notification goroutine to finish" notify=no ``` Then logged in with the primary admin account to find; "The email or password provided is incorrect. Please check for typos and try logging in again." I attempted alternative accounts and, as luck would have it, my backup account sufficed. However, I decided to take the precaution of changing the primary administrator's password and logging back in. It's worth noting that you should always ensure that you have a backup administrative account established – doing so can save considerable inconvenience in the long run.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#135535