starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 12 Packages Projects Releases 10 Wiki Activity

unable to update Open WebUI #2076

New Issue
Closed
opened 2026-02-05 03:39:58 +03:00 by OVERLORD · 11 comments
OVERLORD commented 2026-02-05 03:39:58 +03:00
Owner
Copy Link

Originally created by @Drknght4 on GitHub (Nov 26, 2025).

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

open webui v0.6.40

📂 What was the exact command used to execute the script?

used "update " in the LXC

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

9.0.11

📝 Provide a clear and concise description of the issue.

tried to update the Open WebUI LXC using the "update" method and it installed per the script. once I open the Open WebUI, it still shows that an update is available. i rebooted the LXC, tried to update again and still same issue.

🔄 Steps to reproduce the issue.

step 1:) go to LXC Console
step 2:) log in as root
step 3:) type "update"

⏳ Updating Open WebUI via uvopen-webui[all] is already installed
✔️ Updated Open WebUI
✔️ Updated successfully!

❌ Paste the full error output (if available).

⏳ Updating Open WebUI via uvopen-webui[all] is already installed
✔️ Updated Open WebUI
✔️ Updated successfully!

🖼️ Additional context (optional).

No response

Originally created by @Drknght4 on GitHub (Nov 26, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? open webui v0.6.40 ### 📂 What was the exact command used to execute the script? used "update " in the LXC ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 9.0.11 ### 📝 Provide a clear and concise description of the issue. tried to update the Open WebUI LXC using the "update" method and it installed per the script. once I open the Open WebUI, it still shows that an update is available. i rebooted the LXC, tried to update again and still same issue. ### 🔄 Steps to reproduce the issue. step 1:) go to LXC Console step 2:) log in as root step 3:) type "update" ⏳ Updating Open WebUI via uv`open-webui[all]` is already installed ✔️ Updated Open WebUI ✔️ Updated successfully! ### ❌ Paste the full error output (if available). ⏳ Updating Open WebUI via uv`open-webui[all]` is already installed ✔️ Updated Open WebUI ✔️ Updated successfully! ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 03:39:58 +03:00
OVERLORD commented 2026-02-05 03:40:06 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 26, 2025):

uv tool upgrade --python 3.12 open-webui[all]

there docu is faulty. we have reported it

@MickLesk commented on GitHub (Nov 26, 2025): `uv tool upgrade --python 3.12 open-webui[all]` there docu is faulty. we have reported it
OVERLORD commented 2026-02-05 03:40:13 +03:00
Author
Owner
Copy Link

@Drknght4 commented on GitHub (Nov 26, 2025):

@MickLesk

uv tool upgrade --python 3.12 open-webui[all]

there docu is faulty. we have reported it

Any Solution as of yet? or link the correct git issue page to follow?

Thank you

@Drknght4 commented on GitHub (Nov 26, 2025): @MickLesk > uv tool upgrade --python 3.12 open-webui[all] > > there docu is faulty. we have reported it Any Solution as of yet? or link the correct git issue page to follow? Thank you
OVERLORD commented 2026-02-05 03:40:14 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 26, 2025):

?? Solution is written ?

@MickLesk commented on GitHub (Nov 26, 2025): ?? Solution is written ?
OVERLORD commented 2026-02-05 03:40:17 +03:00
Author
Owner
Copy Link

@shuperluu commented on GitHub (Nov 26, 2025):

@MickLesk

uv tool upgrade --python 3.12 open-webui[all]
there docu is faulty. we have reported it

Any Solution as of yet? or link the correct git issue page to follow?

Thank you

If you run uv tool upgrade --python 3.12 open-webui[all] it will get solved. I was at v0.6.37 and having the same issue to jump to v0.6.40.

@shuperluu commented on GitHub (Nov 26, 2025): > [@MickLesk](https://github.com/MickLesk) > > > uv tool upgrade --python 3.12 open-webui[all] > > there docu is faulty. we have reported it > > Any Solution as of yet? or link the correct git issue page to follow? > > Thank you If you run `uv tool upgrade --python 3.12 open-webui[all]` it will get solved. I was at v0.6.37 and having the same issue to jump to v0.6.40.
OVERLORD commented 2026-02-05 03:40:23 +03:00
Author
Owner
Copy Link

@StaRipper commented on GitHub (Dec 26, 2025):

Same in v0.6.41
(v0.6.43 available!)

@StaRipper commented on GitHub (Dec 26, 2025): Same in v0.6.41 [(v0.6.43 available!)](https://github.com/open-webui/open-webui/releases/tag/v0.6.43)
OVERLORD commented 2026-02-05 03:40:26 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Dec 26, 2025):

uv package is not released for 0.6.43.

@tremor021 commented on GitHub (Dec 26, 2025): `uv` package is not released for 0.6.43.
OVERLORD commented 2026-02-05 03:40:28 +03:00
Author
Owner
Copy Link

@Drknght4 commented on GitHub (Dec 26, 2025):

@MickLesk uv package is not released for 0.6.43. how do advise to proceed?

@Drknght4 commented on GitHub (Dec 26, 2025): @MickLesk uv package is not released for 0.6.43. how do advise to proceed?
OVERLORD commented 2026-02-05 03:40:32 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 26, 2025):

write there maintainer, its not our package. Create an Issue at their repo and ask. They recommend uv, we use uv

@MickLesk commented on GitHub (Dec 26, 2025): write there maintainer, its not our package. Create an Issue at their repo and ask. They recommend uv, we use uv
OVERLORD commented 2026-02-05 03:40:36 +03:00
Author
Owner
Copy Link

@ndom91 commented on GitHub (Jan 3, 2026):

Looks like they've fixed it upstream (https://github.com/open-webui/open-webui/issues/20188).

However, since we're on an old version what does that mean for us (pve script users). Are we stuck in this old version without manual intervention? Or should the update then "just work" once they release the fix to main?

@ndom91 commented on GitHub (Jan 3, 2026): Looks like they've fixed it upstream (https://github.com/open-webui/open-webui/issues/20188). However, since we're on an old version what does that mean for us (pve script users). Are we stuck in this old version without manual intervention? Or should the update then "just work" once they release the fix to `main`?
OVERLORD commented 2026-02-05 03:40:38 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 3, 2026):

Its an uv package. So wait. We dont have any to do with this packaging

@MickLesk commented on GitHub (Jan 3, 2026): Its an uv package. So wait. We dont have any to do with this packaging
OVERLORD commented 2026-02-05 03:40:40 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Jan 3, 2026):

Looks like they've fixed it upstream (open-webui/open-webui#20188).

However, since we're on an old version what does that mean for us (pve script users). Are we stuck in this old version without manual intervention? Or should the update then "just work" once they release the fix to main?

Probably best to wait for a new release. I guess thats when they will merge the fix

@tremor021 commented on GitHub (Jan 3, 2026): > Looks like they've fixed it upstream ([open-webui/open-webui#20188](https://github.com/open-webui/open-webui/issues/20188)). > > However, since we're on an old version what does that mean for us (pve script users). Are we stuck in this old version without manual intervention? Or should the update then "just work" once they release the fix to `main`? Probably best to wait for a new release. I guess thats when they will merge the fix
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2076
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?