starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 17:26:03 +03:00

[GH-ISSUE #7562] openwebui update, ollama fragile #1613

New issue

Closed

opened 2026-02-26 12:49:38 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 12:49:38 +03:00

Owner

Originally created by @grimwiz on GitHub (Sep 10, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/7562

✅ Have you read and understood the above guidelines?

yes

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

openwebui.sh

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/Proxmo xVE/main/ct/openwebui.sh)"

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.11-1-pve)

📝 Provide a clear and concise description of the issue.

running update on openwebui sometimes fails with the following error and rather than recovering or failing gracefully it leaves the instance permanently broken until manually repaired:

⠇ Updating Ollamacurl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)
⠼ Updating Ollama
[ERROR] in line 38: exit code 0: while executing command curl -fsSLO https://ollama.com/download/ollama-linux-amd64.tgz

Whilst the particular error may be due to a network issue, the failure at this point is after the existing ollama has been removed and it doesn't retry, so it needs to be manually fixed before the system functionality is restored.

The download of the new version of the ollama installation tar file should occur before the old version is removed, and only if it's successful should the deletion of the old version take place. This would mean that in the case of a failure the system keeps working, and it doesn't trigger the "I have no ollama" state which means repeating the update fails to repair the damage.

🔄 Steps to reproduce the issue.

❌ Paste the full error output (if available).

🖼️ Additional context (optional).

The ollama update fragment of the update script should be written in a safer way, as follows... by moving the curl command up to before the deletion then if it bombs out it does so before deleting the old version - leaving it outdated but still functional and it will still respect the test at the top of the stanza whether ollama should be installed:

if [ -x "/usr/bin/ollama" ]; then
msg_info "Updating Ollama"
OLLAMA_VERSION=$(ollama -v | awk '{print $NF}')
RELEASE=$(curl -s https://api.github.com/repos/ollama/ollama/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4)}')
if [ "$OLLAMA_VERSION" != "$RELEASE" ]; then
curl -fsSLO https://ollama.com/download/ollama-linux-amd64.tgz
rm -rf /usr/lib/ollama
rm -rf /usr/bin/ollama
tar -C /usr -xzf ollama-linux-amd64.tgz
rm -rf ollama-linux-amd64.tgz
msg_ok "Ollama updated to version $RELEASE"
else
msg_ok "Ollama is already up to date."
fi

Additional information for manual fixes until this change is applied:
For those struggling with downloading a large file, different curl options can help the download succeed, by adding the "-C" argument it can continue an interrupted download:
curl -fsSLOC - https://ollama.com/download/ollama-linux-amd64.tgz --http1.1

Originally created by @grimwiz on GitHub (Sep 10, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/7562 ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? openwebui.sh ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/Proxmo xVE/main/ct/openwebui.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.11-1-pve) ### 📝 Provide a clear and concise description of the issue. running update on openwebui sometimes fails with the following error and rather than recovering or failing gracefully it leaves the instance permanently broken until manually repaired: ⠇ Updating Ollamacurl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1) ⠼ Updating Ollama [ERROR] in line 38: exit code 0: while executing command curl -fsSLO https://ollama.com/download/ollama-linux-amd64.tgz Whilst the particular error may be due to a network issue, the failure at this point is after the existing ollama has been removed and it doesn't retry, so it needs to be manually fixed before the system functionality is restored. The download of the new version of the ollama installation tar file should occur before the old version is removed, and only if it's successful should the deletion of the old version take place. This would mean that in the case of a failure the system keeps working, and it doesn't trigger the "I have no ollama" state which means repeating the update fails to repair the damage. ### 🔄 Steps to reproduce the issue. log in as root, type "update". The error is intermittent and depends on external factors. ### ❌ Paste the full error output (if available). ⠇ Updating Ollamacurl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1) ⠼ Updating Ollama [ERROR] in line 38: exit code 0: while executing command curl -fsSLO https://ollama.com/download/ollama-linux-amd64.tgz ### 🖼️ Additional context (optional). The ollama update fragment of the update script should be written in a safer way, as follows... by moving the curl command up to before the deletion then if it bombs out it does so before deleting the old version - leaving it outdated but still functional and it will still respect the test at the top of the stanza whether ollama should be installed: if [ -x "/usr/bin/ollama" ]; then msg_info "Updating Ollama" OLLAMA_VERSION=$(ollama -v | awk '{print $NF}') RELEASE=$(curl -s https://api.github.com/repos/ollama/ollama/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4)}') if [ "$OLLAMA_VERSION" != "$RELEASE" ]; then curl -fsSLO https://ollama.com/download/ollama-linux-amd64.tgz rm -rf /usr/lib/ollama rm -rf /usr/bin/ollama tar -C /usr -xzf ollama-linux-amd64.tgz rm -rf ollama-linux-amd64.tgz msg_ok "Ollama updated to version $RELEASE" else msg_ok "Ollama is already up to date." fi Additional information for manual fixes until this change is applied: For those struggling with downloading a large file, different curl options can help the download succeed, by adding the "-C" argument it can continue an interrupted download: curl -fsSLOC - https://ollama.com/download/ollama-linux-amd64.tgz --http1.1

kerem

2026-02-26 12:49:38 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:49:38 +03:00

Author

Owner

@MickLesk commented on GitHub (Sep 11, 2025):

The whole issue is described in detail, but basically it's because the Ollama package now has 1.3GB and the repo is not stable.

But basically, why not just make a PR with a fix? That would probably have been faster than describing the issue ^^ After all, it's only 2-4 lines.

@MickLesk commented on GitHub (Sep 11, 2025): The whole issue is described in detail, but basically it's because the Ollama package now has 1.3GB and the repo is not stable. But basically, why not just make a PR with a fix? That would probably have been faster than describing the issue ^^ After all, it's only 2-4 lines.

kerem commented

2026-02-26 12:49:38 +03:00

Author

Owner

@grimwiz commented on GitHub (Sep 11, 2025):

I don't know how to make pr's. Let me look into that.

alternate email: @.***

On Thu, 11 Sept 2025, 07:40 CanbiZ, @.***> wrote:

MickLesk left a comment (community-scripts/ProxmoxVE#7562)
https://github.com/community-scripts/ProxmoxVE/issues/7562#issuecomment-3278480659

The whole issue is described in detail, but basically it's because the
Ollama package now has 1.3GB and the repo is not stable.

But basically, why not just make a PR with a fix? That would probably have
been faster than describing the issue ^^ After all, it's only 2-4 lines.

—
Reply to this email directly, view it on GitHub
https://github.com/community-scripts/ProxmoxVE/issues/7562#issuecomment-3278480659,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEHHNUA5XOEWADYVC37FDBD3SEKODAVCNFSM6AAAAACGFSUJMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENZYGQ4DANRVHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@grimwiz commented on GitHub (Sep 11, 2025): I don't know how to make pr's. Let me look into that. alternate email: ***@***.*** On Thu, 11 Sept 2025, 07:40 CanbiZ, ***@***.***> wrote: > *MickLesk* left a comment (community-scripts/ProxmoxVE#7562) > <https://github.com/community-scripts/ProxmoxVE/issues/7562#issuecomment-3278480659> > > The whole issue is described in detail, but basically it's because the > Ollama package now has 1.3GB and the repo is not stable. > > But basically, why not just make a PR with a fix? That would probably have > been faster than describing the issue ^^ After all, it's only 2-4 lines. > > — > Reply to this email directly, view it on GitHub > <https://github.com/community-scripts/ProxmoxVE/issues/7562#issuecomment-3278480659>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEHHNUA5XOEWADYVC37FDBD3SEKODAVCNFSM6AAAAACGFSUJMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENZYGQ4DANRVHE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

kerem commented

2026-02-26 12:49:38 +03:00

Author

Owner

@HeedfulCrayon commented on GitHub (Sep 21, 2025):

@MickLesk this also affects openwebui install as well

@HeedfulCrayon commented on GitHub (Sep 21, 2025): @MickLesk this also affects openwebui install as well

kerem referenced this issue

2026-02-26 13:32:57 +03:00

[PR #1613] [MERGED] Feature: Add xCaddy for external Modules on Caddy-LXC #3261

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#1613

No description provided.

Rows
Columns