github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 10:58:17 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #263] BUG: Ollama does not report correct version properly, so ollama-webui errors when loading the interface #12010

New Issue
Closed
opened 2026-04-19 18:44:19 -05:00 by GiteaMirror · 12 comments
GiteaMirror commented 2026-04-19 18:44:19 -05:00
Owner
Copy Link

Originally created by @sjclayton on GitHub (Dec 22, 2023).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/263

Describe the bug

When I open the web UI, I am greeted with this error message Connection Issue or Update Needed followed by Oops! It seems like your Ollama needs a little attention. We've detected either a connection hiccup or observed that you're using an older version. Ensure you're on the latest Ollama version (version 0.1.16 or higher) or check your connection. If I close this pop-up, everything works normally.

Running a test connection to http://127.0.0.1:11434/api/version reports 0.0.0

It would appear that Ollama does not actually report the current version as of this time through the API, also I get the same result from running ollama --version on the command line.

To Reproduce
Steps to reproduce the behavior:

 1. Open the Web UI in browser.

Environment

 * OS: Arch Linux
 * Browser: Firefox 121
 * Ollama Version 0.1.17
Originally created by @sjclayton on GitHub (Dec 22, 2023). Original GitHub issue: https://github.com/open-webui/open-webui/issues/263 **Describe the bug** When I open the web UI, I am greeted with this error message `Connection Issue or Update Needed` followed by `Oops! It seems like your Ollama needs a little attention. We've detected either a connection hiccup or observed that you're using an older version. Ensure you're on the latest Ollama version (version 0.1.16 or higher) or check your connection.` If I close this pop-up, everything works normally. Running a test connection to `http://127.0.0.1:11434/api/version` reports `0.0.0` It would appear that Ollama does not actually report the current version as of this time through the API, also I get the same result from running `ollama --version` on the command line. **To Reproduce** Steps to reproduce the behavior: 1. Open the Web UI in browser. ## Environment * OS: Arch Linux * Browser: Firefox 121 * Ollama Version 0.1.17
GiteaMirror commented 2026-04-19 18:44:20 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Dec 22, 2023):

Hi! Could you tell us more about your installation method that was required in the form? Also, if the version api route doesn't output the correct ollama version, that might be ollama's issue not the webui. Thanks!

<!-- gh-comment-id:1868125889 --> @tjbck commented on GitHub (Dec 22, 2023): Hi! Could you tell us more about your installation method that was required in the form? Also, if the version api route doesn't output the correct ollama version, that might be ollama's issue not the webui. Thanks!
GiteaMirror commented 2026-04-19 18:44:20 -05:00
Author
Owner
Copy Link

@sjclayton commented on GitHub (Dec 22, 2023):

I am running the Web-UI only through Docker, Ollama is installed via Pacman.

Yes, the issue might be theirs... but from what I can tell they have never reported any version but 0.0.0 through that API call... so having the Web-UI check for something that it won't get seems like an issue.

EDIT: They added the initial code for a version string like 4 months ago, but it has never been set to an actual version number.

<!-- gh-comment-id:1868128027 --> @sjclayton commented on GitHub (Dec 22, 2023): I am running the Web-UI only through Docker, Ollama is installed via Pacman. Yes, the issue might be theirs... but from what I can tell they have never reported any version but 0.0.0 through that API call... so having the Web-UI check for something that it won't get seems like an issue. EDIT: They added the initial code for a version string like 4 months ago, but it has never been set to an actual version number.
GiteaMirror commented 2026-04-19 18:44:21 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Dec 23, 2023):

Hi, The desktop/docker version of Ollama include the api route that functions properly, so maybe pacman might be the culprit here? Could you try installing Ollama using other installation methods? Thanks!

FYI, here's a screenshot of what it should look like:

image
<!-- gh-comment-id:1868179706 --> @tjbck commented on GitHub (Dec 23, 2023): Hi, The desktop/docker version of Ollama include the api route that functions properly, so maybe pacman might be the culprit here? Could you try installing Ollama using other installation methods? Thanks! FYI, here's a screenshot of what it should look like: <img width="600" alt="image" src="https://github.com/ollama-webui/ollama-webui/assets/25473318/df6a7dbe-01d0-4489-b248-a5777af02ab8">
GiteaMirror commented 2026-04-19 18:44:21 -05:00
Author
Owner
Copy Link

@melanopsis commented on GitHub (Dec 23, 2023):

I can confirm that this is a packaging issue on Arch. The webui works fine if I pull and run the ollama docker image.

<!-- gh-comment-id:1868215915 --> @melanopsis commented on GitHub (Dec 23, 2023): I can confirm that this is a packaging issue on Arch. The webui works fine if I pull and run the ollama docker image.
GiteaMirror commented 2026-04-19 18:44:22 -05:00
Author
Owner
Copy Link

@anuraagdjain commented on GitHub (Dec 23, 2023):

Same issue with home-brew on Mac. Had to uninstall the home-brew version and install the app from the official website.

<!-- gh-comment-id:1868308099 --> @anuraagdjain commented on GitHub (Dec 23, 2023): Same issue with home-brew on Mac. Had to uninstall the home-brew version and install the app from the official website.
GiteaMirror commented 2026-04-19 18:44:23 -05:00
Author
Owner
Copy Link

@nerdenough commented on GitHub (Dec 23, 2023):

Same issue when cloning Ollama manually and building Ollama's Dockerfile. Can be worked around by replacing 0.0.0 with an actual version number is ollama/version/version.go and rebuilding.

<!-- gh-comment-id:1868376775 --> @nerdenough commented on GitHub (Dec 23, 2023): Same issue when cloning Ollama manually and building Ollama's Dockerfile. Can be worked around by replacing `0.0.0` with an actual version number is `ollama/version/version.go` and rebuilding.
GiteaMirror commented 2026-04-19 18:44:26 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Dec 23, 2023):

Seems like we might have to create this issue on the Ollama GitHub repo as well. If anyone creates one, please link this issue!

<!-- gh-comment-id:1868391783 --> @tjbck commented on GitHub (Dec 23, 2023): Seems like we might have to create this issue on the Ollama GitHub repo as well. If anyone creates one, please link this issue!
GiteaMirror commented 2026-04-19 18:44:27 -05:00
Author
Owner
Copy Link

@sjclayton commented on GitHub (Dec 24, 2023):

I can confirm that this is a packaging issue on Arch. The webui works fine if I pull and run the ollama docker image.

Same here, have it running fine now using the docker image for ollama with the web-ui also running in docker.

<!-- gh-comment-id:1868455590 --> @sjclayton commented on GitHub (Dec 24, 2023): > I can confirm that this is a packaging issue on Arch. The webui works fine if I pull and run the ollama docker image. Same here, have it running fine now using the docker image for ollama with the web-ui also running in docker.
GiteaMirror commented 2026-04-19 18:44:28 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Dec 25, 2023):

I'll close this issue for now, but if anyone wants to create an issue on Ollama repo, feel free to link this issue! Thanks!

<!-- gh-comment-id:1868707644 --> @tjbck commented on GitHub (Dec 25, 2023): I'll close this issue for now, but if anyone wants to create an issue on Ollama repo, feel free to link this issue! Thanks!
GiteaMirror commented 2026-04-19 18:44:29 -05:00
Author
Owner
Copy Link

@ThatOneCalculator commented on GitHub (Dec 27, 2023):

Can 0.0.0 be whitelisted as a version?

<!-- gh-comment-id:1869840865 --> @ThatOneCalculator commented on GitHub (Dec 27, 2023): Can `0.0.0` be whitelisted as a version?
GiteaMirror commented 2026-04-19 18:44:29 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Dec 27, 2023):

@ThatOneCalculator, will try to whitelist w/ #216, Stay tuned!

<!-- gh-comment-id:1869843824 --> @tjbck commented on GitHub (Dec 27, 2023): @ThatOneCalculator, will try to whitelist w/ #216, Stay tuned!
GiteaMirror commented 2026-04-19 18:44:30 -05:00
Author
Owner
Copy Link

@ThatOneCalculator commented on GitHub (Dec 27, 2023):

Awesome, thank you!

<!-- gh-comment-id:1869845871 --> @ThatOneCalculator commented on GitHub (Dec 27, 2023): Awesome, thank you!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#12010
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?