mirror of
https://github.com/open-webui/open-webui.git
synced 2026-03-18 04:51:23 -05:00
Remote Ollama server: Model Selection Issue #963
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#963
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 @SamuelDevdas on GitHub (May 18, 2024).
Discussed in https://github.com/open-webui/open-webui/discussions/2359
Originally posted by SamuelDevdas May 17, 2024
Bug Report
Description
Bug Summary:
[When using ollama installed on remote server using docker, how to select models?(
)]
Steps to Reproduce:
[Outline the steps to reproduce the bug. Be as detailed as possible.]
Expected Behavior:
[Available models should be listed, or an options while setting up docker container should be available]
Actual Behavior:
[Models not available to select, thus chat cant be started]
Environment
Open WebUI Version: [e.g., 0.1.120]
Ollama (if applicable): [e.g., 0.1.30, 0.1.32-rc1]
Operating System: [raspbian]
Browser (if applicable): [e.g., Chrome 100.0]
Reproduction Details
Confirmation:
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Installation Method
[Describe the method you used to install the project, e.g., manual installation, Docker, package manager, etc.]
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!