mirror of
https://github.com/open-webui/open-webui.git
synced 2026-03-22 06:02:06 -05:00
Openai connection errors and "No models found" in list #1827
Reference in New Issue
Block a user
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?
Originally created by @mootfrost on GitHub (Aug 20, 2024).
Bug Report
Installation Method
[Describe the method you used to install the project, e.g., git clone, Docker, pip, etc.]
Docker
Environment
Open WebUI Version: [e.g., v0.3.11] v0.3.13
Ollama (if applicable): [e.g., v0.2.0, v0.1.32-rc1] disabled
Operating System: [e.g., Windows 10, macOS Big Sur, Ubuntu 20.04] Debian 11
Browser (if applicable): [e.g., Chrome 100.0, Firefox 98.0] Any browser
Confirmation:
Expected Behavior:
All openai models present in models list.
[Describe what you expected to happen.]
Actual Behavior:
Sometimes list is empty and "No results found" displayed instead.
[Describe what actually happened.]
Description
Bug Summary:
[Provide a brief but clear summary of the bug]
List is failing to load in 8/10 cases.
I'm not using ollama but still getting errors related to this.
Reproduction Details
Steps to Reproduce:
[Outline the steps to reproduce the bug. Be as detailed as possible.]
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Nothing strange, just empty response from /api/v1/models
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
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!