Error 500 after updating OpenWebUI #1340

Closed
opened 2026-02-05 00:25:19 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @Externalnet on GitHub (Jul 25, 2025).

Have you read and understood the above guidelines?

yes

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

OpenWebUI

📂 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?

No response

📝 Provide a clear and concise description of the issue.

After updating OpenWebUI to the latest version I got an error 500

Here I read that npm install --force is required for the time being, or add npmFlags = [ "--force" "--legacy-peer-deps" ];

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

Could this maybe be the issue I get an error 500 after upgrading to the latest version of Open-WebUI ?
If so please change the update script

🔄 Steps to reproduce the issue.

Update Open-WebUI LXC to the lastest version

Paste the full error output (if available).

Error 500 after updating

🖼️ Additional context (optional).

No response

Originally created by @Externalnet on GitHub (Jul 25, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? OpenWebUI ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📝 Provide a clear and concise description of the issue. After updating OpenWebUI to the latest version I got an error 500 Here I read that npm install --force is required for the time being, or add npmFlags = [ "--force" "--legacy-peer-deps" ]; https://github.com/open-webui/open-webui/issues/15880 Could this maybe be the issue I get an error 500 after upgrading to the latest version of Open-WebUI ? If so please change the update script ### 🔄 Steps to reproduce the issue. Update Open-WebUI LXC to the lastest version ### ❌ Paste the full error output (if available). Error 500 after updating ### 🖼️ Additional context (optional). _No response_
Author
Owner

@tremor021 commented on GitHub (Jul 25, 2025):

check your logs, you wouldn't be able to update if --force wasn't used. The script is doing it already

@tremor021 commented on GitHub (Jul 25, 2025): check your logs, you wouldn't be able to update if --force wasn't used. The script is doing it already
Author
Owner

@MickLesk commented on GitHub (Jul 25, 2025):

Force is already present?

@MickLesk commented on GitHub (Jul 25, 2025): Force is already present?
Author
Owner

@Externalnet commented on GitHub (Jul 25, 2025):

Very very strange I ran the update again in vebose mode to look for possible errors/warnings. This time the update was succesfull and I do not have an error 500. Thanks for the quick response, please close the ticket

@Externalnet commented on GitHub (Jul 25, 2025): Very very strange I ran the update again in vebose mode to look for possible errors/warnings. This time the update was succesfull and I do not have an error 500. Thanks for the quick response, please close the ticket
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1340