github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-11 10:34:13 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #15613] issue: Chromadb attempting to send posthog telemetry #17617

New Issue
Closed
opened 2026-04-19 23:25:08 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-19 23:25:08 -05:00
Owner
Copy Link

Originally created by @KodeMunkie on GitHub (Jul 9, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15613

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

0.6.15

Ollama Version (if applicable)

No response

Operating System

Linux Mint 22.1

Browser (if applicable)

No response

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using 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 every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

OpenWebUI's chromadb should not send telemetry, or attempt to send telemetry.

Actual Behavior

Unknown what has caused this - the only chromadb specific line I see is the following, but I have attached a screenshot with further context below. Nb. I'm not comfortable providing all logs.

2025-07-09 19:02:57.367 | ERROR | chromadb.telemetry.product.posthog:_direct_capture:61 - Failed to send telemetry event ClientCreateCollectionEvent: capture() takes 1 positional argument but 3 were given - {}

Steps to Reproduce

Apologies, as stated I have no idea how this was produced (I just noticed it a few days in the openwebui log after it occurred), however I do know to disable the telemetry in Chromadb a flag must be set to opt out, please see https://docs.trychroma.com/docs/overview/telemetry.

Please can you ensure you set this flag to resolve this issue?

Logs & Screenshots

Image

Additional Information

No response

Originally created by @KodeMunkie on GitHub (Jul 9, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/15613 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version 0.6.15 ### Ollama Version (if applicable) _No response_ ### Operating System Linux Mint 22.1 ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using 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 every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior OpenWebUI's chromadb should not send telemetry, or attempt to send telemetry. ### Actual Behavior Unknown what has caused this - the only chromadb specific line I see is the following, but I have attached a screenshot with further context below. Nb. I'm not comfortable providing all logs. 2025-07-09 19:02:57.367 | ERROR | chromadb.telemetry.product.posthog:_direct_capture:61 - Failed to send telemetry event ClientCreateCollectionEvent: capture() takes 1 positional argument but 3 were given - {} ### Steps to Reproduce Apologies, as stated I have no idea how this was produced (I just noticed it a few days in the openwebui log after it occurred), however I do know to disable the telemetry in Chromadb a flag must be set to opt out, please see https://docs.trychroma.com/docs/overview/telemetry. Please can you ensure you set this flag to resolve this issue? ### Logs & Screenshots <img width="2141" height="428" alt="Image" src="https://github.com/user-attachments/assets/ba95f7c4-ee4c-4846-8c3f-676ad7536756" /> ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-19 23:25:08 -05:00
GiteaMirror commented 2026-04-19 23:25:11 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Jul 10, 2025):

Please check our dockerfile. ANONYMIZED_TELEMETRY=false is being set by default, and chromadb should honour the env var.

<!-- gh-comment-id:3056747176 --> @tjbck commented on GitHub (Jul 10, 2025): Please check our `dockerfile`. `ANONYMIZED_TELEMETRY=false` is being set by default, and chromadb should honour the env var.
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 bug
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#17617
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?