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 13 Packages Projects Releases 10 Wiki Activity

Oct 5th commit for OpenWebUI unable to update from previous version. #1934

New Issue
Closed
opened 2026-02-05 02:54:07 +03:00 by OVERLORD · 7 comments
OVERLORD commented 2026-02-05 02:54:07 +03:00
Owner
Copy Link

Originally created by @novafire99 on GitHub (Nov 6, 2025).

Originally assigned to: @tremor021 on GitHub.

✅ Have you read and understood the above guidelines?

yes

📜 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 12

📈 Which Proxmox version are you on?

9.0.11

📝 Provide a clear and concise description of the issue.

Commit fb1a558 no longer allows an existing install to update.

🔄 Steps to reproduce the issue.

Simply using the update command.

Now shows that "No Open WebUI Installation Found!", even though it's fully working older version, I normally run an update once a week, last update Oct 30th.

❌ Paste the full error output (if available).

/ __ ____ ___ ____ | | / /__ / /_ / / / / /
/ / / / __ / _ / __ \ | | /| / / _ / __ / / / // /
/ // / // / __/ / / / | |/ |/ / __/ // / // // /
_/ ./_// // |/|/_/./_//
//
💡 Warning: Storage is dangerously low (83%).
Continue anyway? [y/N] y

✖️ No Open WebUI Installation Found!
(It's not low on space, there is still 17GB free, it's 100GB for the drive)

🖼️ Additional context (optional).

According to the commit it now uses Debian 13 for the LXC, and has moved the install from the /opt/open-webui directory to in the /root/.open-webui folder. This change no longer allows updating from the previous version.

It would be nice if this is the new layout if it upgraded the LXC to Debian 13 and if that is the new location for the data to be stored, it be moved to the new location and run the update for the application.

Originally created by @novafire99 on GitHub (Nov 6, 2025). Originally assigned to: @tremor021 on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 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 12 ### 📈 Which Proxmox version are you on? 9.0.11 ### 📝 Provide a clear and concise description of the issue. Commit fb1a558 no longer allows an existing install to update. ### 🔄 Steps to reproduce the issue. Simply using the update command. Now shows that "No Open WebUI Installation Found!", even though it's fully working older version, I normally run an update once a week, last update Oct 30th. ### ❌ Paste the full error output (if available). ____ _ __ __ __ ______ / __ \____ ___ ____ | | / /__ / /_ / / / / _/ / / / / __ \/ _ \/ __ \ | | /| / / _ \/ __ \/ / / // / / /_/ / /_/ / __/ / / / | |/ |/ / __/ /_/ / /_/ // / \____/ .___/\___/_/ /_/ |__/|__/\___/_.___/\____/___/ /_/ 💡 Warning: Storage is dangerously low (83%). Continue anyway? [y/N] y ✖️ No Open WebUI Installation Found! (It's not low on space, there is still 17GB free, it's 100GB for the drive) ### 🖼️ Additional context (optional). According to the commit it now uses Debian 13 for the LXC, and has moved the install from the /opt/open-webui directory to in the /root/.open-webui folder. This change no longer allows updating from the previous version. It would be nice if this is the new layout if it upgraded the LXC to Debian 13 and if that is the new location for the data to be stored, it be moved to the new location and run the update for the application.
OVERLORD added the breaking change label 2026-02-05 02:54:07 +03:00
OVERLORD commented 2026-02-05 02:54:20 +03:00
Author
Owner
Copy Link

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

@tremor021 - In my opinion, it will only be possible to reinstall OpenWebUI. The problem is that they have changed a lot of dependencies and set the entire installation routine to UVX, which we cannot migrate for users. Especially since there are ~25 versions and not every user has the same

@MickLesk commented on GitHub (Nov 6, 2025): @tremor021 - In my opinion, it will only be possible to reinstall OpenWebUI. The problem is that they have changed a lot of dependencies and set the entire installation routine to UVX, which we cannot migrate for users. Especially since there are ~25 versions and not every user has the same
OVERLORD commented 2026-02-05 02:54:28 +03:00
Author
Owner
Copy Link

@novafire99 commented on GitHub (Nov 6, 2025):

OK that's fine, but the upgrade script should then at least state that then. That due to OS upgrade for LXC and dependency changes for new OS that it needs to be reinstalled to keep things simple and clean. Right now it's cryptic, I also find it unusual that it was moved to the root account directory from /opt, but that is just my opinion, as long as it works it doesn't matter. Just want to help with the user experience. Along with the note that it needs to br reinstalled, indicate to users that want to keep their config/chat history how to back it up and restore it.

@novafire99 commented on GitHub (Nov 6, 2025): OK that's fine, but the upgrade script should then at least state that then. That due to OS upgrade for LXC and dependency changes for new OS that it needs to be reinstalled to keep things simple and clean. Right now it's cryptic, I also find it unusual that it was moved to the root account directory from /opt, but that is just my opinion, as long as it works it doesn't matter. Just want to help with the user experience. Along with the note that it needs to br reinstalled, indicate to users that want to keep their config/chat history how to back it up and restore it.
OVERLORD commented 2026-02-05 02:54:34 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Nov 6, 2025):

This is the offical installation method, described in their documentation. https://docs.openwebui.com/getting-started/quick-start/#installation-with-uv
DATA_DIR is set to what is used in their documentation, its not unusual, its in their docs. https://docs.openwebui.com/getting-started/quick-start/#2-run-open-webui

I'm not sure if DATA from previous script is compatible with this install method, hence why i said in the PR that fresh install is needed, to ensure data compatibility. In this case its /root/.open-webui and our update script is looking for this directory specificaly, as its not existing in old LXCs and it prevents upgrades = broken containers.

https://github.com/community-scripts/ProxmoxVE/pull/8874#issue-3590646445
This installation method is much much simpler to deal with and will ensure that no issue is caused by our script, as entire installation is contained within uvx package
Also, container OS is bumped to Debian 13 to be up to date with other scripts and the host OS as well.

@tremor021 commented on GitHub (Nov 6, 2025): This is the offical installation method, described in their documentation. https://docs.openwebui.com/getting-started/quick-start/#installation-with-uv DATA_DIR is set to what is used in their documentation, its not unusual, its in their docs. https://docs.openwebui.com/getting-started/quick-start/#2-run-open-webui I'm not sure if DATA from previous script is compatible with this install method, hence why i said in the PR that fresh install is needed, to ensure data compatibility. In this case its `/root/.open-webui` and our update script is looking for this directory specificaly, as its not existing in old LXCs and it prevents upgrades = broken containers. https://github.com/community-scripts/ProxmoxVE/pull/8874#issue-3590646445 This installation method is much much simpler to deal with and will ensure that no issue is caused by our script, as entire installation is contained within `uvx` package Also, container OS is bumped to Debian 13 to be up to date with other scripts and the host OS as well.
OVERLORD commented 2026-02-05 02:54:38 +03:00
Author
Owner
Copy Link

@novafire99 commented on GitHub (Nov 6, 2025):

I meant that unusual as it changed previous behaviour that wasn't expected, making it look like something broke and the user not know where to start to fix it. I'm only bring this up because it caught me by surprise (unexpected change in behaviour), I have no problem deailing with it, but i know a lot of people still learning are not going to know what to do. If it at least it had a notice in the update stating the change and that it needs to be redeployed to bring it up to date. It doesn't need a full explanation of the process, just a notice so that the user can do the research necessary to migrate their data or just delete and redeploy. This should really apply to any app that is deplyed by the scripts to give a consistant user experiance.

@novafire99 commented on GitHub (Nov 6, 2025): I meant that unusual as it changed previous behaviour that wasn't expected, making it look like something broke and the user not know where to start to fix it. I'm only bring this up because it caught me by surprise (unexpected change in behaviour), I have no problem deailing with it, but i know a lot of people still learning are not going to know what to do. If it at least it had a notice in the update stating the change and that it needs to be redeployed to bring it up to date. It doesn't need a full explanation of the process, just a notice so that the user can do the research necessary to migrate their data or just delete and redeploy. This should really apply to any app that is deplyed by the scripts to give a consistant user experiance.
OVERLORD commented 2026-02-05 02:54:47 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Nov 6, 2025):

We can add a note to the website (as noone really reads PR's it seems) stating that all installs before Nov 5 are considered obsolete and new LXC should be deployed.

Can you try moving your existing data to this new LXC install? If it recognizes it properly, then i guess we can try making a upgrade procedure... idk, just spitballing here

@tremor021 commented on GitHub (Nov 6, 2025): We can add a note to the website (as noone really reads PR's it seems) stating that all installs before Nov 5 are considered obsolete and new LXC should be deployed. Can you try moving your existing data to this new LXC install? If it recognizes it properly, then i guess we can try making a upgrade procedure... idk, just spitballing here
OVERLORD commented 2026-02-05 02:54:52 +03:00
Author
Owner
Copy Link

@BoberMod commented on GitHub (Nov 9, 2025):

Can you try moving your existing data to this new LXC install?

@tremor021, I moved the backend/data directories, and it recognizes them properly and works fine: I got all conversations, users, functions, custom models, API keys, etc. Sessions are lost, so users should re-login to their account.

However, now unsure whether I want to use the Open WebUI installation from community scripts. In my opinion, the maintainer would do that check "if it works", not people finding it accidentally after the instance is already broken because of the updater introduced breaking changes without notice.

There is still no warning on the community scripts website, no message in the updater, no link to PR. This issue is closed without a decision.

If the maintenance team can't keep up with proper updates of all scripts, it makes sense to deprecate/remove such scripts, as their updates are introducing more problems than resolving.
Especially in this case, it's easy to move out because you have already started using uvx (which, btw, is not enforced by OWUI team) and it can be done with the same simplicity as the community script bash one-liner.

@BoberMod commented on GitHub (Nov 9, 2025): > Can you try moving your existing data to this new LXC install? @tremor021, I moved the `backend/data `directories, and it recognizes them properly and works fine: I got all conversations, users, functions, custom models, API keys, etc. Sessions are lost, so users should re-login to their account. ------- However, now unsure whether I want to use the Open WebUI installation from community scripts. In my opinion, the maintainer would do that check "if it works", not people finding it accidentally after the instance is already broken because of the updater introduced breaking changes without notice. There is still no warning on the community scripts website, no message in the updater, no link to PR. This issue is closed without a decision. If the maintenance team can't keep up with proper updates of all scripts, it makes sense to deprecate/remove such scripts, as their updates are introducing more problems than resolving. Especially in this case, it's easy to move out because you have already started using `uvx` (which, btw, is not enforced by OWUI team) and it can be done with the same simplicity as the community script bash one-liner.
OVERLORD commented 2026-02-05 02:54:55 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Nov 9, 2025):

Can you try moving your existing data to this new LXC install?

@tremor021, I moved the backend/data directories, and it recognizes them properly and works fine: I got all conversations, users, functions, custom models, API keys, etc. Sessions are lost, so users should re-login to their account.

This is good to hear, as i don't use the app and have no clue what it does.

However, now unsure whether I want to use the Open WebUI installation from community scripts. In my opinion, the maintainer would do that check "if it works", not people finding it accidentally after the instance is already broken because of the updater introduced breaking changes without notice.

The update is broken already by Open WebUI. Its not the updater that introduced the breaking change, its the broken dependency chain when using their other official installation method, via pip. This has nothing to do with us, its upstream problem. How is this unclear, it beats me.... We cant fix upstream problems...

There is still no warning on the community scripts website, no message in the updater, no link to PR. This issue is closed without a decision.

Like i said, updater DOES NOTHING to your data, it DOESNT RUN as it now looks for new data directory. You have official documentation URL? you can update the app yourself, like the Open WebUI developers intended. Read the documentation. Wait for them to fix the pip way of updating and continue maintaining YOUR LXC as you should.

If the maintenance team can't keep up with proper updates of all scripts, it makes sense to deprecate/remove such scripts, as their updates are introducing more problems than resolving. Especially in this case, it's easy to move out because you have already started using uvx (which, btw, is not enforced by OWUI team) and it can be done with the same simplicity as the community script bash one-liner.

Again, OFFICIAL installation method via pip has broken dependency chain, its NOT A SCRIPT ISSUE. uvx installation method is more reliable, hence why we switch to it. THE PROBLEM WITH THIS APP HAS NOTHING TO DO WITH MAITENANCE TEAM!. I'm sounding like a broken record now already...

I'm using caps lock on purpose here, because users like you talk about stuff they don't understand. Like in this instance you keep saying that its broken update script, its maintenance teams job to fix it, etc etc. This is not our issue, its Open WebUI installation issue when using one of their official installation methods. Lucky for you they have few of them and the one we choose to support going forward should be reliable than the others.

Regarding the website warning etc. Even though they are not put up yet, it doesn't matter. We are not breaking your LXC, your app continues to work fine, your data is intact. You can continue maintaining your LXC like everyone does. Read the documentation on how to do it. If you wish to switch to our new LXC, you need to deploy a new LXC and move your data. It can't be simpler than that...

@tremor021 commented on GitHub (Nov 9, 2025): > > Can you try moving your existing data to this new LXC install? > > [@tremor021](https://github.com/tremor021), I moved the `backend/data `directories, and it recognizes them properly and works fine: I got all conversations, users, functions, custom models, API keys, etc. Sessions are lost, so users should re-login to their account. This is good to hear, as i don't use the app and have no clue what it does. > > However, now unsure whether I want to use the Open WebUI installation from community scripts. In my opinion, the maintainer would do that check "if it works", not people finding it accidentally after the instance is already broken because of the updater introduced breaking changes without notice. The update is broken already by Open WebUI. Its not the updater that introduced the breaking change, its the broken dependency chain when using their other official installation method, via `pip`. This has nothing to do with us, its upstream problem. How is this unclear, it beats me.... We cant fix upstream problems... > > There is still no warning on the community scripts website, no message in the updater, no link to PR. This issue is closed without a decision. Like i said, updater DOES NOTHING to your data, it DOESNT RUN as it now looks for new data directory. You have official documentation URL? you can update the app yourself, like the Open WebUI developers intended. Read the documentation. Wait for them to fix the `pip` way of updating and continue maintaining YOUR LXC as you should. > > If the maintenance team can't keep up with proper updates of all scripts, it makes sense to deprecate/remove such scripts, as their updates are introducing more problems than resolving. Especially in this case, it's easy to move out because you have already started using `uvx` (which, btw, is not enforced by OWUI team) and it can be done with the same simplicity as the community script bash one-liner. Again, OFFICIAL installation method via `pip` has broken dependency chain, its NOT A SCRIPT ISSUE. `uvx` installation method is more reliable, hence why we switch to it. THE PROBLEM WITH THIS APP HAS NOTHING TO DO WITH MAITENANCE TEAM!. I'm sounding like a broken record now already... I'm using caps lock on purpose here, because users like you talk about stuff they don't understand. Like in this instance you keep saying that its broken update script, its maintenance teams job to fix it, etc etc. This is not our issue, its Open WebUI installation issue when using one of their official installation methods. Lucky for you they have few of them and the one we choose to support going forward should be reliable than the others. Regarding the website warning etc. Even though they are not put up yet, it doesn't matter. We are not breaking your LXC, your app continues to work fine, your data is intact. You can continue maintaining your LXC like everyone does. Read the documentation on how to do it. If you wish to switch to our new LXC, you need to deploy a new LXC and move your data. It can't be simpler than that...
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 breaking change
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#1934
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?