github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 19:38:46 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #10435] Manual install fails on v0.5.15 with "unsupported engine". Works on v0.5.14 #31421

New Issue
Closed
opened 2026-04-25 05:22:39 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-25 05:22:39 -05:00
Owner
Copy Link

Originally created by @mattcaron on GitHub (Feb 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/10435

Bug Report

Installation Method

Manual install based on development instructions (and I swear there used to be docs on how to do this, but I can't find them anymore).

Environment

  • Open WebUI Version: v0.5.15

  • Ollama (if applicable): v0.5.11

  • Operating System: Ubuntu 24.04

  • Browser (if applicable): Firefox 135.0

Confirmation:

  • I have read and followed all the instructions provided in the README.md.
  • I am on the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs. - N/A
  • I have included the Docker container logs. - N/A
  • I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:

Install succeeds without error.

Actual Behavior:

npm install fails with error:

(matt@bluebox) ~/storage1/ai/open-webui ((v0.5.15))$ npm install
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: undici@7.3.0
npm ERR! notsup Not compatible with your version of node/npm: undici@7.3.0
npm ERR! notsup Required: {"node":">=20.18.1"}
npm ERR! notsup Actual:   {"npm":"9.2.0"}

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/matt/.npm/_logs/2025-02-20T14_51_31_588Z-debug-0.log

Description

Bug Summary:

Following the instructions here: https://docs.openwebui.com/getting-started/advanced-topics/development#-local-development-setup

And synthesizing them into a local production upgrade, e.g.:

npm install
npm run build
source venv/bin/activate
pip install -r backend/requirements.txt -U

(No need to create the venv, it exists already)

The first step fails with the above shown error.

Reproduction Details

Steps to Reproduce:

From soup to nuts:

git clone https://github.com/open-webui/open-webui.git
cd open-webui
git checkout v0.5.14
npm install
npm run build
python3.11 -m venv venv
source venv/bin/activate
pip install --upgrade pip
pip install -r backend/requirements.txt -U
deactivate
# All of the above work for me.
git checkout v0.5.15
npm install  # <--- This step fails. Should succeed.
npm run build
source venv/bin/activate
pip install -r backend/requirements.txt -U

Logs and Screenshots

Log:
2025-02-20T14_51_31_588Z-debug-0.log

Browser Console Logs:
N/A - not happening in browser.

Docker Container Logs:
N/A - Not using docker

Screenshots/Screen Recordings (if applicable):
N/A - see copy paste in "Actual behavior".

Additional Information

I fully realize this may be a PEBTAC problem, because the operator was fed non-updated development instructions. If there is some other command that should be run, docs likely need to be updated.

Oh, and because I expect it will rapidly become relevant:

(matt@bluebox) ~$ node --version
v18.19.1
(matt@bluebox) ~$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=24.04
DISTRIB_CODENAME=noble
DISTRIB_DESCRIPTION="Ubuntu 24.04.2 LTS"
Originally created by @mattcaron on GitHub (Feb 20, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/10435 # Bug Report ## Installation Method Manual install based on development instructions (and I swear there used to be docs on how to do this, but I can't find them anymore). ## Environment - **Open WebUI Version:** v0.5.15 - **Ollama (if applicable):** v0.5.11 - **Operating System:** Ubuntu 24.04 - **Browser (if applicable):** Firefox 135.0 **Confirmation:** - [X] I have read and followed all the instructions provided in the README.md. - [X] I am on the latest version of both Open WebUI and Ollama. - [ ] I have included the browser console logs. - N/A - [ ] I have included the Docker container logs. - N/A - [X] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below. ## Expected Behavior: Install succeeds without error. ## Actual Behavior: `npm install` fails with error: ``` (matt@bluebox) ~/storage1/ai/open-webui ((v0.5.15))$ npm install npm ERR! code EBADENGINE npm ERR! engine Unsupported engine npm ERR! engine Not compatible with your version of node/npm: undici@7.3.0 npm ERR! notsup Not compatible with your version of node/npm: undici@7.3.0 npm ERR! notsup Required: {"node":">=20.18.1"} npm ERR! notsup Actual: {"npm":"9.2.0"} npm ERR! A complete log of this run can be found in: npm ERR! /home/matt/.npm/_logs/2025-02-20T14_51_31_588Z-debug-0.log ``` ## Description **Bug Summary:** Following the instructions here: https://docs.openwebui.com/getting-started/advanced-topics/development#-local-development-setup And synthesizing them into a local production upgrade, e.g.: ``` npm install npm run build source venv/bin/activate pip install -r backend/requirements.txt -U ``` (No need to create the venv, it exists already) The first step fails with the above shown error. ## Reproduction Details **Steps to Reproduce:** From soup to nuts: ``` git clone https://github.com/open-webui/open-webui.git cd open-webui git checkout v0.5.14 npm install npm run build python3.11 -m venv venv source venv/bin/activate pip install --upgrade pip pip install -r backend/requirements.txt -U deactivate # All of the above work for me. git checkout v0.5.15 npm install # <--- This step fails. Should succeed. npm run build source venv/bin/activate pip install -r backend/requirements.txt -U ``` ## Logs and Screenshots Log: [2025-02-20T14_51_31_588Z-debug-0.log](https://github.com/user-attachments/files/18888390/2025-02-20T14_51_31_588Z-debug-0.log) **Browser Console Logs:** N/A - not happening in browser. **Docker Container Logs:** N/A - Not using docker **Screenshots/Screen Recordings (if applicable):** N/A - see copy paste in "Actual behavior". ## Additional Information I fully realize this may be a PEBTAC problem, because the operator was fed non-updated development instructions. If there is some other command that should be run, docs likely need to be updated. Oh, and because I expect it will rapidly become relevant: ``` (matt@bluebox) ~$ node --version v18.19.1 (matt@bluebox) ~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=24.04 DISTRIB_CODENAME=noble DISTRIB_DESCRIPTION="Ubuntu 24.04.2 LTS" ```
GiteaMirror commented 2026-04-25 05:22:40 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Feb 20, 2025):

Node 22 is required!

<!-- gh-comment-id:2672361878 --> @tjbck commented on GitHub (Feb 20, 2025): Node 22 is required!
GiteaMirror commented 2026-04-25 05:22:41 -05:00
Author
Owner
Copy Link

@mattcaron commented on GitHub (Feb 20, 2025):

Ah, thank you. So, not a regression. I can't say that I'm surprised by this answer, FWIW.

For anyone finding this, if you're lazy, you can do this to update Node.js on any debianish system:

~$ curl -fsSL https://deb.nodesource.com/setup_22.x | sudo bash - 
~$ sudo apt-get install -y nodejs

If you don't trust random scripts from the internet, do this:

  1. Add key

    wget -O- https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --no-default-keyring --keyring=/usr/share/keyrings/nodesource.gpg --import

  2. Create /etc/apt/sources.list.d/nodesource.list as follows (change arch as necessary):

    deb [arch=amd64 signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_22.x nodistro main

  3. Create /etc/apt/preferences.d/nsolid as follows:

    Package: nsolid
Pin: origin deb.nodesource.com
Pin-Priority: 600

  4. Create /etc/apt/preferences.d/nodejs as follows:

    Package: nodejs
Pin: origin deb.nodesource.com
Pin-Priority: 600

  5. Fix perms:

    sudo chmod a+r /etc/apt/sources.list.d/nodesource.list /etc/apt/preferences.d/nsolid /etc/apt/preferences.d/nodejs

  6. Install it:

    sudo apt update
sudo apt install -y nodejs

Once this is done, v0.5.15 installs and runs using the process described in the bug report.

<!-- gh-comment-id:2672441498 --> @mattcaron commented on GitHub (Feb 20, 2025): Ah, thank you. So, not a regression. I can't say that I'm surprised by this answer, FWIW. For anyone finding this, if you're lazy, you can do this to update Node.js on any debianish system: ``` ~$ curl -fsSL https://deb.nodesource.com/setup_22.x | sudo bash - ~$ sudo apt-get install -y nodejs ``` If you don't trust random scripts from the internet, do this: 1. Add key wget -O- https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --no-default-keyring --keyring=/usr/share/keyrings/nodesource.gpg --import 1. Create `/etc/apt/sources.list.d/nodesource.list` as follows (change `arch` as necessary): deb [arch=amd64 signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_22.x nodistro main 1. Create `/etc/apt/preferences.d/nsolid` as follows: Package: nsolid Pin: origin deb.nodesource.com Pin-Priority: 600 1. Create `/etc/apt/preferences.d/nodejs` as follows: Package: nodejs Pin: origin deb.nodesource.com Pin-Priority: 600 1. Fix perms: sudo chmod a+r /etc/apt/sources.list.d/nodesource.list /etc/apt/preferences.d/nsolid /etc/apt/preferences.d/nodejs 1. Install it: sudo apt update sudo apt install -y nodejs Once this is done, v0.5.15 installs and runs using the process described in the bug report.
GiteaMirror commented 2026-04-25 05:22:41 -05:00
Author
Owner
Copy Link

@hipatiaLavender commented on GitHub (Feb 27, 2025):

Thanks to @mattcaron, after reading your very useful comment I managed to get webui built again. Strange thing is the webui server now says it is version v0.5.16, (should have been v0.5.17) plus the client says v0.5.18 is now available - so I can do it all again tomorrow!

<!-- gh-comment-id:2689234616 --> @hipatiaLavender commented on GitHub (Feb 27, 2025): Thanks to @mattcaron, after reading your very useful comment I managed to get webui built again. Strange thing is the webui server now says it is version v0.5.16, (should have been v0.5.17) plus the client says v0.5.18 is now available - so I can do it all again tomorrow!
GiteaMirror commented 2026-04-25 05:22:42 -05:00
Author
Owner
Copy Link

@merrime-n commented on GitHub (May 5, 2025):

I had Node v18. As soon as I read @tjbck 's reply I changed the Node version and it worked.

Here's what you need to do:

# install nvm
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.5/install.sh | bash
# list the versions
nvm ls-remote
# install Node v22 (LTS)
nvm install <version>
# make it the default Node
nvm alias default <version>
# confirm
node -v

Then you can run npm install with no problems.

<!-- gh-comment-id:2849985088 --> @merrime-n commented on GitHub (May 5, 2025): I had Node v18. As soon as I read @tjbck 's reply I changed the Node version and it worked. Here's what you need to do: ```bash # install nvm curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.5/install.sh | bash # list the versions nvm ls-remote # install Node v22 (LTS) nvm install <version> # make it the default Node nvm alias default <version> # confirm node -v ``` Then you can run `npm install` with no problems.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#31421
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?