mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-28 17:59:25 -05:00
Ollama connection test in admin connection settings fails with improper injection of 'ollama in api URL #1623
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#1623
Reference in New Issue
Block a user
Originally created by @hillct on GitHub (Jul 27, 2024).
Bug Report
The Ollama connection test as available in Admin Connection settings fails returning a 500 server error (strangely, because ollama returns a 404) when the test button is clicked in the build deployed in the official v3.10 docker image
ghcr.io/open-webui/open-webui:mainDescription
It appears that the Ollama api version endpoint is being called via a passthrough method within the Open-Webui API
http://192.168.1.10:8080/ollama/api/versionin my example, which should simply pass through the version property value from the Ollama API version endpoint,http://192.168.1.10:11434/api/versionin my example, but is for some reason, returning a 404 status{"detail":"Not Found"}rather than simply passing through the value supplied by Ollama, which in my case is the commitish hash for my Ollama build{"version":"f2a96c7"}with a 200 OKBug Summary:
As above, the bug is limited to failure of the ollama connectivity test in the admin connection settings which has the added impact of preventing changes to the default ollama api URL, from being saved, for any users who have deployed Ollama at a non-default location.
This issue does not impact operational Ollama connectivity throughout the rest of the application, for example listing available Ollama models, or using them via the new chat page.
Steps to Reproduce:
Deploy Open-webui docker image most recently pushed
v3.10and an ollama build that is between tagged versions, in my case, most recent from themainbranch. The Ollama api version endpoint will by design intent, contain the hash of the most recent commit, rather than than an integer version. Visit the admin connections settings page and attempt to verify Ollama connection using the UI button. A toast notification will be displayed saying Connection Failed. Vrify he scope of he buf by checking the the Ollama API version endpoint directly for example:http://192.168.1.10:11434/api/versionExpected Behavior:
In the default configuration, where the Ollama API base URL is
http://host.docker.internal:11434the manual ollama connectivity test should be performed by querying the version endpoint `http://192.168.1.17:8080/api/version which should then return the proper version value as reported from the Ollama API, in my case, the hash representing the the most recent git commit made to the deployd Ollama build, with a 200 status code.Actual Behavior:
The manual connectivity test fails even though Ollama is clearly available at the target location, as verified by manually querying the Ollama API.
It's not completely clear why non-numeric Ollama version identifiers are not being passed through without issue, but ha operaion is apparently being performed here: https://github.com/open-webui/open-webui/blob/main/src/lib/apis/ollama/index.ts#L138-L168
Environment
Open WebUI Version: 3.10
Ollama (if applicable): Commit f2a96c7 whih is a few after the v0.3.0 release
Operating System: Ubuntu 22.04.4 LTS
Browser (if applicable): Chrome 126.0.6478.183 (but not applicable to this issue)
Reproduction Details
As above. The Docker logs yield more details as to where vrsion is being evaluated as an integer
Confirmation:
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Installation Method
Docker (official) pull for Opn-WebUI
For Ollama, as detailed here: https://github.com/dusty-nv/jetson-containers/tree/master/packages/llm/ollama
not pull, but build, when prompted. It should be noted that Open-WebUI v3.8 worked with this Ollama build.
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!