mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 02:48:13 -05:00
Settings -> Ollama Server URL: Getting rid of pitfalls #138
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#138
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 @bavcol on GitHub (Dec 29, 2023).
Is your feature request related to a problem? Please describe.
I am new to ollama and ollama-webui and I was surprised how easy the default setup (localhost) was.
Next step was to run ollama and ollama-webui on different machines. I got it running eventually. But in retrospective, there were some pitfalls regarding Settings -> Ollama Server URL which made it unnecessary hard for me (and maybe for others as well).
Describe the solution you'd like
Feature 1: Improve advertisement of the UI-feature Settings -> Ollama Server URL
From README -> Features:
and from README -> Accessing External Ollama on a Different Server
This made me think there's (not yet) a convenient way to change the Ollama Server URL from within the UI and I have to use the environment variable.
Imo changing the Ollama Server URL in the UI should be advertised as the preferred way in the README (for the first time user). Setting the environment variable is worth mentioning as an alternative for the experienced user.
Feature 2: Improve default value of Settings -> Ollama Server URL
I suggest using http://localhost:11434/api as the default value. It shows the required url pattern and hints at the required url features (http:// & /api) and is easy to recognize ("Ah, this is the localhost:11434 from ollama!").
The current value /ollama/api seems pretty random to me.
Feature 3: Get rid of cumbersome required URL parts http:// and /api
I am used to enter localhost:11434 to check if my local ollama server is running:
However, localhost:11434 fails when entered in Settings -> Ollama Server URL:
Same for http://localhost:11434 and localhost:11434/api.
Only http://localhost:11434/api succeeds:
Describe alternatives you've considered
-/-
Additional context
I use Windows 11 + WSL2 + Docker Desktop to run Ollama and Ollama WebUI.
I am a hobby user and don't have much experience in Linux, Docker and LLMs, but thanks to your awesome projects ollama and ollama-webui I still was able to "chat with my PC" ❤️
I have some experience in python and git, so if you agree on my suggested features I might be able to contribute (at least some of) those myself.
Also let me know if I should create separate issues for the suggested features. I thought it's a good idea to keep it all in one place, but I'm unsure if that's the right way to do it.
@tjbck commented on GitHub (Dec 29, 2023):
Hi, Thanks for the thorough feature request! FYI, Ollama WebUI consists of two primary components: the frontend and the backend (which serves as a reverse proxy, handling static frontend files, and additional features). Having the ollama api url set to
/ollama/api(reverse proxy route) is a design choice we made on purpose, the reason being, it allows us to ensure enhanced security by securing the ollama api route. If you wish to only use the frontend for the webui, you might want to check out our stripped down version of ollama-webui that's being actively worked on: https://github.com/ollama-webui/ollama-webui-liteI'll close this as not planned but I'll update the documentation and the help messages in the webui to reflect your concerns and to address any future confusions based on your request, Thanks a lot!
@bavcol commented on GitHub (Dec 29, 2023):
I will keep an eye on https://github.com/ollama-webui/ollama-webui-lite :)
The updates in the Settings -> Ollama API URL and Troubleshooting.md are helping me understand. In the future I will use
OLLAMA_API_BASE_URLenvironment variable.What about adding another field Ollama API base URL to the UI Settings, so it can be conveniently set from within the UI, like Ollama API URL (instead of having to use the
OLLAMA_API_BASE_URLenvironment variable)?@DailyDisco commented on GitHub (Jan 4, 2025):
This helped a bunch thanks