github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-08-30 17:25:30 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #8783] ChromaDB version changed in latest release, breaking compatibility with existing deployments #134980

New Issue
Closed
opened 2026-05-25 01:29:51 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-05-25 01:29:51 -05:00
Owner
Copy Link
Copy Source

Originally created by @bielids on GitHub (Jan 23, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8783

Bug Report

Installation Method

Kubernetes deployment with 2 pods; one for Chroma and the other for Open WebUI

Environment

  • Open WebUI Version: 0.5.6
  • Chroma Version: 0.5.15

Confirmation:

  • I have read and followed all the instructions provided in the README.md.
  • I am on the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:

Authentication to ChromaDB should succeed

Actual Behavior:

It fails due to a 404 response from ChromaDB as the auth endpoint is missing in ChromaDB 0.5.15

Description

Bug Summary:
Chroma dependency requirement changed from Open WebUI 0.5.4 (Chroma 0.5.15) to 0.5.6 (Chroma 0.6.2)

Reproduction Details

Install ChromaDB 0.5.15 and connect Open WebUI 0.5.4 to it. Next, upgrade Open WebUI to 0.5.6

Logs and Screenshots

Docker Container Logs:

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/chromadb/api/base_http_client.py", line 99, in _raise_chroma_error
    resp.raise_for_status()
  File "/usr/local/lib/python3.11/site-packages/httpx/_models.py", line 829, in raise_for_status
    raise HTTPStatusError(message, request=request, response=self)
httpx.HTTPStatusError: Client error '404 Not Found' for url 'http://chroma:8000/api/v2/auth/identity'
For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404

$ podman run -ti ghcr.io/open-webui/open-webui:0.5.4 python -c 'import chromadb; c = chromadb.Client(); print(c.get_version())'
0.5.15
$ podman run -ti ghcr.io/open-webui/open-webui:0.5.5 python -c 'import chromadb; c = chromadb.Client(); print(c.get_version())'
0.6.2
$ podman run -ti ghcr.io/open-webui/open-webui:0.5.6 python -c 'import chromadb; c = chromadb.Client(); print(c.get_version())'
0.6.2

Additional Information

Could you please adjust the release notes to mention this change so that people can upgrade their ChromaDB instance without issues. I installed ChromaDB 0.5.15 as this is what's used in the Open WebUI image and wasn't aware of the change until my deployment failed. Upgrading ChromaDB to 0.6.2 resolved my issues.

Originally created by @bielids on GitHub (Jan 23, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/8783 # Bug Report ## Installation Method Kubernetes deployment with 2 pods; one for Chroma and the other for Open WebUI ## Environment - **Open WebUI Version:** 0.5.6 - **Chroma Version:** 0.5.15 **Confirmation:** - [X] I have read and followed all the instructions provided in the README.md. - [X] I am on the latest version of both Open WebUI and Ollama. - [X] I have included the browser console logs. - [X] I have included the Docker container logs. - [X] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below. ## Expected Behavior: Authentication to ChromaDB should succeed ## Actual Behavior: It fails due to a 404 response from ChromaDB as the auth endpoint is missing in ChromaDB 0.5.15 ## Description **Bug Summary:** Chroma dependency requirement changed from Open WebUI 0.5.4 (Chroma 0.5.15) to 0.5.6 (Chroma 0.6.2) ## Reproduction Details Install ChromaDB 0.5.15 and connect Open WebUI 0.5.4 to it. Next, upgrade Open WebUI to 0.5.6 ## Logs and Screenshots **Docker Container Logs:** ``` Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/chromadb/api/base_http_client.py", line 99, in _raise_chroma_error resp.raise_for_status() File "/usr/local/lib/python3.11/site-packages/httpx/_models.py", line 829, in raise_for_status raise HTTPStatusError(message, request=request, response=self) httpx.HTTPStatusError: Client error '404 Not Found' for url 'http://chroma:8000/api/v2/auth/identity' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404 ``` ``` $ podman run -ti ghcr.io/open-webui/open-webui:0.5.4 python -c 'import chromadb; c = chromadb.Client(); print(c.get_version())' 0.5.15 $ podman run -ti ghcr.io/open-webui/open-webui:0.5.5 python -c 'import chromadb; c = chromadb.Client(); print(c.get_version())' 0.6.2 $ podman run -ti ghcr.io/open-webui/open-webui:0.5.6 python -c 'import chromadb; c = chromadb.Client(); print(c.get_version())' 0.6.2 ``` ## Additional Information Could you please adjust the release notes to mention this change so that people can upgrade their ChromaDB instance without issues. I installed ChromaDB 0.5.15 as this is what's used in the Open WebUI image and wasn't aware of the change until my deployment failed. Upgrading ChromaDB to 0.6.2 resolved my issues.
GiteaMirror commented 2026-05-25 01:30:07 -05:00
Author
Owner
Copy Link
Copy Source

@tjbck commented on GitHub (Jan 23, 2025):

External ChromaDB version should match internal Open WebUI ChromaDB version.

<!-- gh-comment-id:2608712627 --> @tjbck commented on GitHub (Jan 23, 2025): External ChromaDB version should match internal Open WebUI ChromaDB version.
GiteaMirror commented 2026-05-25 01:30:09 -05:00
Author
Owner
Copy Link
Copy Source

@bielids commented on GitHub (Jan 23, 2025):

Release notes should say when Chroma DB version is updated.

I did match the version, in case where you didn't see my notes, but knowing this ahead of time via release notes would have made this much less painful.

<!-- gh-comment-id:2608716860 --> @bielids commented on GitHub (Jan 23, 2025): Release notes should say when Chroma DB version is updated. I did match the version, in case where you didn't see my notes, but knowing this ahead of time via release notes would have made this much less painful.
GiteaMirror commented 2026-05-25 01:30:12 -05:00
Author
Owner
Copy Link
Copy Source

@bielids commented on GitHub (Jan 23, 2025):

Release notes still haven't been updated. Please reopen issue.

<!-- gh-comment-id:2608720592 --> @bielids commented on GitHub (Jan 23, 2025): Release notes still haven't been updated. Please reopen issue.
GiteaMirror commented 2026-05-25 01:30:13 -05:00
Author
Owner
Copy Link
Copy Source

@tkg61 commented on GitHub (Jan 23, 2025):

Also have this issue would have liked this in the release notes as well as it is a breaking change. @bielids did you have to do anything to chroma to update or just update the container?

edit: Yes, just updating the container works, no changes needed

<!-- gh-comment-id:2609897436 --> @tkg61 commented on GitHub (Jan 23, 2025): Also have this issue would have liked this in the release notes as well as it is a breaking change. @bielids did you have to do anything to chroma to update or just update the container? edit: Yes, just updating the container works, no changes needed
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 labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#134980