[GH-ISSUE #10543] Update script broken and incorrect command for Open WebUI update #2283

Closed
opened 2026-02-26 12:51:54 +03:00 by kerem · 5 comments
Owner

Originally created by @CamronBorealis on GitHub (Jan 4, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10543

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

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

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.1.4/5ac30304265fbd8e (running kernel: 6.17.2-2-pve)

📝 Provide a clear and concise description of the issue.

First off, just wanted to say "thank you" for continuing tteck's work. I enjoy seeing more scripts come up.

I recently installed Open WebUI. Upon opening, it informed me of an update. I went to the container and ran:

update

It produced the following output:

   ____                      _       __     __    __  ______
  / __ \____  ___  ____     | |     / /__  / /_  / / / /  _/
 / / / / __ \/ _ \/ __ \    | | /| / / _ \/ __ \/ / / // /  
/ /_/ / /_/ /  __/ / / /    | |/ |/ /  __/ /_/ / /_/ // /   
\____/ .___/\___/_/ /_/     |__/|__/\___/_.___/\____/___/   
    /_/                                                     

  ⏳   Updating Open WebUI via uvenvironment: line 128: uv: command not found
  ✖️   in line 128: exit code 127 (Command not found): while executing command  uv tool upgrade --python 3.12 open-webui[all]

Turns out that uv is located at /usr/local/bin/uv and the PATH variable is /sbin:/bin:/usr/sbin:/usr/bin, which makes sense why uv can't be found.

Maybe I need to open a separate ticket for this, but I got it working by instead running:

/usr/local/bin/uv tool upgrade --python 3.12 open-webui[all]

But that didn't actually update the app. I ended up running:

/usr/local/bin/uv tool install --upgrade --python 3.12 open-webui[all]

That actually upgraded the package. So it seems that not only is uv not in PATH, but the command itself is incorrect to upgrade the version. On top of that, I would also say that, since it's been over 2 weeks since this latest version, you probably have to tweak how to get the correct version in the first place.

🔄 Steps to reproduce the issue.

  1. Install Open WebUI
  2. Browse to Open WebUI and see the message about an update being available
  3. In the LXC container, run update

Paste the full error output (if available).

   ____                      _       __     __    __  ______
  / __ \____  ___  ____     | |     / /__  / /_  / / / /  _/
 / / / / __ \/ _ \/ __ \    | | /| / / _ \/ __ \/ / / // /  
/ /_/ / /_/ /  __/ / / /    | |/ |/ /  __/ /_/ / /_/ // /   
\____/ .___/\___/_/ /_/     |__/|__/\___/_.___/\____/___/   
    /_/                                                     

  ⏳   Updating Open WebUI via uvenvironment: line 128: uv: command not found
  ✖️   in line 128: exit code 127 (Command not found): while executing command  uv tool upgrade --python 3.12 open-webui[all]

🖼️ Additional context (optional).

No response

Originally created by @CamronBorealis on GitHub (Jan 4, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10543 ### ✅ 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 ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [ ] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.1.4/5ac30304265fbd8e (running kernel: 6.17.2-2-pve) ### 📝 Provide a clear and concise description of the issue. First off, just wanted to say "thank you" for continuing tteck's work. I enjoy seeing more scripts come up. I recently installed Open WebUI. Upon opening, it informed me of an update. I went to the container and ran: ``` update ``` It produced the following output: ```bash ____ _ __ __ __ ______ / __ \____ ___ ____ | | / /__ / /_ / / / / _/ / / / / __ \/ _ \/ __ \ | | /| / / _ \/ __ \/ / / // / / /_/ / /_/ / __/ / / / | |/ |/ / __/ /_/ / /_/ // / \____/ .___/\___/_/ /_/ |__/|__/\___/_.___/\____/___/ /_/ ⏳ Updating Open WebUI via uvenvironment: line 128: uv: command not found ✖️ in line 128: exit code 127 (Command not found): while executing command uv tool upgrade --python 3.12 open-webui[all] ``` Turns out that `uv` is located at `/usr/local/bin/uv` and the PATH variable is `/sbin:/bin:/usr/sbin:/usr/bin`, which makes sense why `uv` can't be found. Maybe I need to open a separate ticket for this, but I got it working by instead running: ```bash /usr/local/bin/uv tool upgrade --python 3.12 open-webui[all] ``` But that didn't actually update the app. I ended up running: ```bash /usr/local/bin/uv tool install --upgrade --python 3.12 open-webui[all] ``` That actually upgraded the package. So it seems that not only is `uv` not in PATH, but the command itself is incorrect to upgrade the version. On top of that, I would also say that, since it's been over 2 weeks since this latest version, you probably have to tweak how to get the correct version in the first place. ### 🔄 Steps to reproduce the issue. 1. Install Open WebUI 2. Browse to Open WebUI and see the message about an update being available 3. In the LXC container, run `update` ### ❌ Paste the full error output (if available). ```bash ____ _ __ __ __ ______ / __ \____ ___ ____ | | / /__ / /_ / / / / _/ / / / / __ \/ _ \/ __ \ | | /| / / _ \/ __ \/ / / // / / /_/ / /_/ / __/ / / / | |/ |/ / __/ /_/ / /_/ // / \____/ .___/\___/_/ /_/ |__/|__/\___/_.___/\____/___/ /_/ ⏳ Updating Open WebUI via uvenvironment: line 128: uv: command not found ✖️ in line 128: exit code 127 (Command not found): while executing command uv tool upgrade --python 3.12 open-webui[all] ``` ### 🖼️ Additional context (optional). _No response_
kerem 2026-02-26 12:51:54 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 4, 2026):

Hello, it looks like you are referencing the old tteck repo.

This repository is no longer used for active scripts.
Please update your bookmarks and use: https://helper-scripts.com

Also make sure your Bash command starts with:

bash <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/...)

This issue is being closed automatically.

<!-- gh-comment-id:3708546487 --> @github-actions[bot] commented on GitHub (Jan 4, 2026): Hello, it looks like you are referencing the **old tteck repo**. This repository is no longer used for active scripts. **Please update your bookmarks** and use: [https://helper-scripts.com](https://helper-scripts.com) Also make sure your Bash command starts with: ```bash bash <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/...) ``` This issue is being closed automatically.
Author
Owner

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

  1. Uv should Always be in path, expect you use pct enter or something

  2. No its since weeks an Upstream issue, Take a Look in old closed Issues and discussions, we have answered this several Times

<!-- gh-comment-id:3709066494 --> @MickLesk commented on GitHub (Jan 5, 2026): 1. Uv should Always be in path, expect you use pct enter or something 2. No its since weeks an Upstream issue, Take a Look in old closed Issues and discussions, we have answered this several Times
Author
Owner

@CamronBorealis commented on GitHub (Jan 5, 2026):

I think the bot marked this incorrectly, this is still open.

@MickLesk I posted the path and location I found uv. I am not on the host, I am running that inside the LXC container. I did search for issues related to Open WebUI, found none, so maybe point me to the post you're referring to? I installed this yesterday.

<!-- gh-comment-id:3710463280 --> @CamronBorealis commented on GitHub (Jan 5, 2026): I think the bot marked this incorrectly, this is still open. @MickLesk I posted the path and location I found `uv`. I am not on the host, I am running that inside the LXC container. I did search for issues related to Open WebUI, found none, so maybe point me to the post you're referring to? I installed this yesterday.
Author
Owner
<!-- gh-comment-id:3710498838 --> @MickLesk commented on GitHub (Jan 5, 2026): and how are you entered into the lxc? 1min search https://github.com/community-scripts/ProxmoxVE/issues/10434 https://github.com/community-scripts/ProxmoxVE/issues/9447 https://github.com/open-webui/open-webui/issues/20188
Author
Owner

@CamronBorealis commented on GitHub (Jan 5, 2026):

Entering the LXC via Console in web browser.

Thank you for the links. I would expect that the uv upgrade gets the latest package from PyPi, since uv doesn't host a package repo of their own, which would be 0.64.3.

<!-- gh-comment-id:3711608115 --> @CamronBorealis commented on GitHub (Jan 5, 2026): Entering the LXC via Console in web browser. Thank you for the links. I would expect that the uv upgrade gets the latest package from PyPi, since uv doesn't host a package repo of their own, which would be 0.64.3.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#2283
No description provided.