Don't know if this has been changed lately on ollama, but the correct endpoint seems to be /api
To Reproduce
Install ollama separately, then run òllama serveThen run following docker-command:docker run -d -p 3000:8080 --add-host=host.docker.internal:host-gateway --name ollama-webui --restart always ghcr.io/ollama-webui/ollama-webui:main`
It should say connection server failed because the endpoint is /api
Expected behavior
Should maybe mention this in the part of the readme talking about the standalone ollama-webui version
Screenshots
NA
Desktop (please complete the following information):
Debian 11
Chrome 119.0.6045.159
Additional context
Originally created by @Herz3h on GitHub (Nov 27, 2023).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/154
**Describe the bug**
I just pulled this webui with the following docker command:
`docker run -d -p 3000:8080 --add-host=host.docker.internal:host-gateway --name ollama-webui --restart always ghcr.io/ollama-webui/ollama-webui:main`
I already had ollama running separately.
And the default Ollama Server URL was `/ollama/api`
Don't know if this has been changed lately on ollama, but the correct endpoint seems to be `/api`
**To Reproduce**
Install ollama separately, then run òllama serve`
Then run following docker-command: `docker run -d -p 3000:8080 --add-host=host.docker.internal:host-gateway --name ollama-webui --restart always ghcr.io/ollama-webui/ollama-webui:main`
It should say connection server failed because the endpoint is /api
**Expected behavior**
Should maybe mention this in the part of the readme talking about the standalone ollama-webui version
**Screenshots**
NA
**Desktop (please complete the following information):**
- Debian 11
- Chrome 119.0.6045.159
**Additional context**
Hi, Could you verify that both Ollama WebUI and the Ollama instance is running on the same machine? I'll close this for now as /ollama/api route is the backend reverse proxy route which redirects to your Ollama api /api route and is how it's supposed to be by design. Keep us updated, Thanks.
<!-- gh-comment-id:1829141653 -->
@tjbck commented on GitHub (Nov 28, 2023):
Hi, Could you verify that both Ollama WebUI and the Ollama instance is running on the same machine? I'll close this for now as `/ollama/api` route is the backend reverse proxy route which redirects to your Ollama api `/api` route and is how it's supposed to be by design. Keep us updated, Thanks.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Herz3h on GitHub (Nov 27, 2023).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/154
Describe the bug
I just pulled this webui with the following docker command:
docker run -d -p 3000:8080 --add-host=host.docker.internal:host-gateway --name ollama-webui --restart always ghcr.io/ollama-webui/ollama-webui:mainI already had ollama running separately.
And the default Ollama Server URL was
/ollama/apiDon't know if this has been changed lately on ollama, but the correct endpoint seems to be
/apiTo Reproduce
Install ollama separately, then run òllama serve
Then run following docker-command:docker run -d -p 3000:8080 --add-host=host.docker.internal:host-gateway --name ollama-webui --restart always ghcr.io/ollama-webui/ollama-webui:main`It should say connection server failed because the endpoint is /api
Expected behavior
Should maybe mention this in the part of the readme talking about the standalone ollama-webui version
Screenshots
NA
Desktop (please complete the following information):
Additional context
@tjbck commented on GitHub (Nov 28, 2023):
Hi, Could you verify that both Ollama WebUI and the Ollama instance is running on the same machine? I'll close this for now as
/ollama/apiroute is the backend reverse proxy route which redirects to your Ollama api/apiroute and is how it's supposed to be by design. Keep us updated, Thanks.