github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 03:18:23 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #12882] issue: Open WebUI (version 0.5.14) self-updates to 0.6.0. #16742

New Issue
Closed
opened 2026-04-19 22:36:07 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-19 22:36:07 -05:00
Owner
Copy Link

Originally created by @DmitriyAlergant on GitHub (Apr 15, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12882

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

0.5.14

Ollama Version (if applicable)

No response

Operating System

Docker

Browser (if applicable)

No response

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 listed steps to reproduce the bug in detail.

Expected Behavior

Starting an Open-WebUI from a previous version (ex: 0.5.14), I expected this is the version I will be using as I needed at this time. There might be reasons to continue using an outdated version. There is no documented auto-update functionality in Open-WebUI (unless "watchtower" is enabled), so I don't expect any version surprises.

Actual Behavior

Open-WebUI automatically upgrades itself in runtime from 0.5.14 to 0.6.0.

Steps to Reproduce

The following scenario I was able to reproduce several times on the same machine, cleanly.

  1. Clean Docker desktop. Deleted all other images and volumes of Open-WebUI except ghcr.io/open-webui/open-webui:0.5.14 (ImageID d83a6bc2fb7c...), modified 2 months ago.

  2. Starting docker run -d -p 3000:8080 -v open-webui:/app/backend/data --name open-webui ghcr.io/open-webui/open-webui:0.5.14

  3. Open WebUI takes some time (up to a minute) to start. First I can't access port :3000 by browser then I can access but it keeps rotating pretty pictures a few times until Authentication Window comes up and I can create the first user. **Surprisingly, this takes long time - much longer then normally with other versions. I did not even know it is capable of rotating multiple pictures before showing the first login form.

During that time, the log shows v0.5.14 - building the best open-source AI user interface.

https://github.com/open-webui/open-webui

  1. If I do the fist login very quickly as soon as the login form arrives, the front-end is initially at the version 0.5.14 - as reported by User Settings -> About, Admin Settings -> General dialogue, and also the overall capability level, like if I create a user group, its permissions shown Workspace Permissions and Chat Permissions sections - as expected for 0.5.14.

However after subsequent full-page refresh (re-enter the Web UI), it starts showing 0.6.0 (0.6.5 available). What?! Some capabilities are now actually at 0.6.0 level, e.g. I create a user group, its permissions page has a new "Sharing Permissions" section which was only implemented in 0.6.0. Also some pipe functions are broken due to a new tool_servers[] parameter, etc.

  1. If I waited a longer time before doing a first login, I get into 0.6.0 right away.

  2. The WebUI stays at version 0.6.0 after container restarts, assuming I let it start fully and don't log in too quickly.

WHAT IS THIS ?!

Logs & Screenshots

Image

Additional Information

No response

Originally created by @DmitriyAlergant on GitHub (Apr 15, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/12882 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [ ] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version 0.5.14 ### Ollama Version (if applicable) _No response_ ### Operating System Docker ### Browser (if applicable) _No response_ ### Confirmation - [x] 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. - [x] I have listed steps to reproduce the bug in detail. ### Expected Behavior Starting an Open-WebUI from a previous version (ex: 0.5.14), I expected this is the version I will be using as I needed at this time. There might be reasons to continue using an outdated version. There is no documented auto-update functionality in Open-WebUI (unless "watchtower" is enabled), so I don't expect any version surprises. ### Actual Behavior Open-WebUI automatically upgrades itself in runtime from 0.5.14 to 0.6.0. ### Steps to Reproduce **_The following scenario I was able to reproduce several times on the same machine, cleanly._** 1. Clean Docker desktop. Deleted all other images and volumes of Open-WebUI except **ghcr.io/open-webui/open-webui:0.5.14** (ImageID d83a6bc2fb7c...), modified 2 months ago. 2. Starting docker run -d -p 3000:8080 -v open-webui:/app/backend/data --name open-webui ghcr.io/open-webui/open-webui:0.5.14 3. Open WebUI takes some time (up to a minute) to start. First I can't access port :3000 by browser then I can access but it keeps rotating pretty pictures a few times until Authentication Window comes up and I can create the first user. **Surprisingly, this takes long time - much longer then normally with other versions. I did not even know it is capable of rotating multiple pictures before showing the first login form. During that time, the log shows v0.5.14 - building the best open-source AI user interface. **https://github.com/open-webui/open-webui** 4. If I do the fist login very quickly as soon as the login form arrives, the front-end is initially at the version 0.5.14 - as reported by User Settings -> About, Admin Settings -> General dialogue, and also the overall capability level, like if I create a user group, its permissions shown Workspace Permissions and Chat Permissions sections - as expected for 0.5.14. However after subsequent full-page refresh (re-enter the Web UI), it starts showing **0.6.0** (0.6.5 available). What?! Some capabilities are now actually at 0.6.0 level, e.g. I create a user group, its permissions page has a new "Sharing Permissions" section which was only implemented in 0.6.0. Also some pipe functions are broken due to a new tool_servers[] parameter, etc. 5. If I waited a longer time before doing a first login, I get into 0.6.0 right away. 6. The WebUI stays at version 0.6.0 after container restarts, assuming I let it start fully and don't log in too quickly. WHAT IS THIS ?! ### Logs & Screenshots ![Image](https://github.com/user-attachments/assets/df96a5d1-ad05-4f70-b827-75748340196d) ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-19 22:36:07 -05:00
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#16742
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?