github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 06:03:26 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #8657] Docker compose npm install fails on onnxruntime behind corporate proxy #118518

New Issue
Closed
opened 2026-05-20 19:52:13 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-20 19:52:13 -05:00
Owner
Copy Link

Originally created by @McKayMDavis on GitHub (Jan 17, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8657

Bug Report

Installation Method

I git cloned the most recent main branch, then attempted to run in development mode using the Docker setup instructions here: https://docs.openwebui.com/getting-started/advanced-topics/development/.

Environment

  • Open WebUI Version: main branch commit 4269df0

  • Operating System: Windows 10

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.
  • I have included the Docker container logs.
  • I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:

npm reaches out to my internal registry to install dependencies of onnxruntime.

Actual Behavior:

npm reaches out to internal registry as expected for all dependencies except:

npm reaches out to github to install dependencies of onnxruntime-linux-x64-gpu-1.19.2.tgz regardless of npm configuration. This is a known bug with this version of onnxruntime and would be solved by upgrading to the latest version.

Bug:
https://github.com/microsoft/onnxruntime/issues/23231

Fix:
https://github.com/microsoft/onnxruntime/pull/23242

Description

Bug Summary:
See Actual Behavior.

Reproduction Details

Steps to Reproduce:
Attempt Docker development instructions here: https://docs.openwebui.com/getting-started/advanced-topics/development/ from behind a corporate VPN/proxy.

Logs and Screenshots

Browser Console Logs:
[Include relevant browser console logs, if applicable]

Docker Container Logs:

68.96 npm error Downloading "https://github.com/microsoft/onnxruntime/releases/download/v1.19.2/onnxruntime-linux-x64-gpu-1.19.2.tgz"...
68.96 npm error node:internal/deps/undici/undici:13484
68.96 npm error       Error.captureStackTrace(err);
68.96 npm error             ^
68.96 npm error
68.96 npm error TypeError: fetch failed
68.96 npm error     at node:internal/deps/undici/undici:13484:13
68.96 npm error     at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
68.96 npm error   [cause]: Error: self-signed certificate in certificate chain
68.96 npm error       at TLSSocket.onConnectSecure (node:_tls_wrap:1679:34)
68.96 npm error       at TLSSocket.emit (node:events:524:28)
68.96 npm error       at TLSSocket._finishInit (node:_tls_wrap:1078:8)
68.96 npm error       at ssl.onhandshakedone (node:_tls_wrap:864:12) {
68.96 npm error     code: 'SELF_SIGNED_CERT_IN_CHAIN'
68.96 npm error   }
68.96 npm error }
68.96 npm error
68.96 npm error Node.js v22.13.0

Screenshots/Screen Recordings (if applicable):
[Attach any relevant screenshots to help illustrate the issue]

Additional Information

[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]

Note

If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!

Originally created by @McKayMDavis on GitHub (Jan 17, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/8657 # Bug Report ## Installation Method I git cloned the most recent main branch, then attempted to run in development mode using the Docker setup instructions here: https://docs.openwebui.com/getting-started/advanced-topics/development/. ## Environment - **Open WebUI Version:** main branch commit [4269df0](https://github.com/open-webui/open-webui/commit/4269df041fef62208d59babe0faae866d2bfbc3c) - **Operating System:** Windows 10 **Confirmation:** - [x] 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. - [x] I have included the Docker container logs. - [ ] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below. ## Expected Behavior: npm reaches out to my internal registry to install dependencies of onnxruntime. ## Actual Behavior: npm reaches out to internal registry as expected for all dependencies except: npm reaches out to github to install dependencies of onnxruntime-linux-x64-gpu-1.19.2.tgz regardless of npm configuration. *This is a known bug with this version of onnxruntime and would be solved by upgrading to the latest version.* Bug: https://github.com/microsoft/onnxruntime/issues/23231 Fix: https://github.com/microsoft/onnxruntime/pull/23242 ## Description **Bug Summary:** See Actual Behavior. ## Reproduction Details **Steps to Reproduce:** Attempt Docker development instructions here: https://docs.openwebui.com/getting-started/advanced-topics/development/ from behind a corporate VPN/proxy. ## Logs and Screenshots **Browser Console Logs:** [Include relevant browser console logs, if applicable] **Docker Container Logs:** ``` 68.96 npm error Downloading "https://github.com/microsoft/onnxruntime/releases/download/v1.19.2/onnxruntime-linux-x64-gpu-1.19.2.tgz"... 68.96 npm error node:internal/deps/undici/undici:13484 68.96 npm error Error.captureStackTrace(err); 68.96 npm error ^ 68.96 npm error 68.96 npm error TypeError: fetch failed 68.96 npm error at node:internal/deps/undici/undici:13484:13 68.96 npm error at process.processTicksAndRejections (node:internal/process/task_queues:105:5) { 68.96 npm error [cause]: Error: self-signed certificate in certificate chain 68.96 npm error at TLSSocket.onConnectSecure (node:_tls_wrap:1679:34) 68.96 npm error at TLSSocket.emit (node:events:524:28) 68.96 npm error at TLSSocket._finishInit (node:_tls_wrap:1078:8) 68.96 npm error at ssl.onhandshakedone (node:_tls_wrap:864:12) { 68.96 npm error code: 'SELF_SIGNED_CERT_IN_CHAIN' 68.96 npm error } 68.96 npm error } 68.96 npm error 68.96 npm error Node.js v22.13.0 ``` **Screenshots/Screen Recordings (if applicable):** [Attach any relevant screenshots to help illustrate the issue] ## Additional Information [Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.] ## Note If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
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#118518
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?