I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
v0.7.2
Ollama Version (if applicable)
v0.14.2
Operating System
openSUSE Leap 16.0
Browser (if applicable)
Chrome 143.0.7499.193
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
With the ENABLE_OTEL set to true, both the traces and metrics should be sent to the configured endpoint following OTEL_EXPORTER_OTLP_ENDPOINT.
Actual Behavior
Neither traces nor metrics were sent to the configured endpoint.
The logs show a warning as below
2026-01-21 22:38:17.683 | WARNING | opentelemetry.sdk.metrics._internal.metric_reader_storage:_handle_view_instrument_match:280 - Views <opentelemetry.sdk.metrics._internal.view.View object at 0x7f8f8ee4fa50> and <opentelemetry.sdk.metrics._internal.view.View object at 0x7f8f8ee4fa50> will cause conflicting metrics identities
Steps to Reproduce
- ENABLE_OTEL=true
- ENABLE_OTEL_METRICS=true
- ENABLE_OTEL_TRACES=true
- OTEL_EXPORTER_OTLP_PROTOCOL=grpc
- USE_OTEL_HTTP_EXPORTER=true
- OTEL_EXPORTER_OTLP_INSECURE=true# Use insecure connection for OTLP, remove in production
- OTEL_EXPORTER_OTLP_ENDPOINT=http://grafana-otel-lgtm:4317
- OTEL_SERVICE_NAME=open-webui
Start the container with the above environment variables
check the container logs using command docker logs open-webui
there is only one warning message as stated above when the open-webui application started
nothing else where there is no logs related to opentelemetry when doing chat w/ models on open-webui
Logs & Screenshots
Loading WEBUI_SECRET_KEY from file, not provided as an environment variable.
Loading WEBUI_SECRET_KEY from .webui_secret_key
INFO [alembic.runtime.migration] Context impl SQLiteImpl.
INFO [alembic.runtime.migration] Will assume non-transactional DDL.
WARNI [open_webui.env] ⚠️ SECURITY WARNING: JWT_EXPIRES_IN is set to '-1'
See: https://docs.openwebui.com/getting-started/env-configuration
WARNI [open_webui.env]
WARNING: CORS_ALLOW_ORIGIN IS SET TO '*' - NOT RECOMMENDED FOR PRODUCTION DEPLOYMENTS.
/app/backend/open_webui/retrieval/vector/dbs/qdrant_multitenancy.py:77: UserWarning: Api key is used with an insecure connection.
else Qclient(
WARNI [langchain_community.utils.user_agent] USER_AGENT environment variable not set, consider setting it to identify your requests.
██████╗ ██████╗ ███████╗███╗ ██╗ ██╗ ██╗███████╗██████╗ ██╗ ██╗██╗
██╔═══██╗██╔══██╗██╔════╝████╗ ██║ ██║ ██║██╔════╝██╔══██╗██║ ██║██║
██║ ██║██████╔╝█████╗ ██╔██╗ ██║ ██║ █╗ ██║█████╗ ██████╔╝██║ ██║██║
██║ ██║██╔═══╝ ██╔══╝ ██║╚██╗██║ ██║███╗██║██╔══╝ ██╔══██╗██║ ██║██║
╚██████╔╝██║ ███████╗██║ ╚████║ ╚███╔███╔╝███████╗██████╔╝╚██████╔╝██║
╚═════╝ ╚═╝ ╚══════╝╚═╝ ╚═══╝ ╚══╝╚══╝ ╚══════╝╚═════╝ ╚═════╝ ╚═╝
v0.7.2 - building the best AI user interface.
https://github.com/open-webui/open-webui
Fetching 13 files: 100%|██████████| 13/13 [00:00<00:00, 160843.52it/s]
INFO: Started server process [1]
INFO: Waiting for application startup.
2026-01-21 22:38:16.746 | INFO | open_webui.utils.logger:start_logger:166 - GLOBAL_LOG_LEVEL: INFO
2026-01-21 22:38:16.746 | INFO | open_webui.main:lifespan:604 - Installing external dependencies of functions and tools...
2026-01-21 22:38:16.760 | INFO | open_webui.utils.plugin:install_frontmatter_requirements:286 - No requirements found in frontmatter.
2026-01-21 22:38:17.682 | INFO | uvicorn.protocols.http.httptools_impl:send:483 - 10.118.20.181:0 - "GET /ws/socket.io/?EIO=4&transport=polling&t=PlW_V8S HTTP/1.0"200 - {"trace_id": "ff152a2a3de4d9663d662fee62743ad1", "span_id": "293c3abb49e926f3"}
2026-01-21 22:38:17.683 | WARNING | opentelemetry.sdk.metrics._internal.metric_reader_storage:_handle_view_instrument_match:280 - Views <opentelemetry.sdk.metrics._internal.view.View object at 0x7f8f8ee4fa50> and <opentelemetry.sdk.metrics._internal.view.View object at 0x7f8f8ee4fa50> will cause conflicting metrics identities
Additional Information
No response
Originally created by @tnndclub on GitHub (Jan 21, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20840
### Check Existing Issues
- [x] I have searched for any existing and/or related issues.
- [x] I have searched for any existing and/or related discussions.
- [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
v0.7.2
### Ollama Version (if applicable)
v0.14.2
### Operating System
openSUSE Leap 16.0
### Browser (if applicable)
Chrome 143.0.7499.193
### 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
With the ENABLE_OTEL set to true, both the traces and metrics should be sent to the configured endpoint following OTEL_EXPORTER_OTLP_ENDPOINT.
### Actual Behavior
Neither traces nor metrics were sent to the configured endpoint.
The logs show a warning as below
```shell
2026-01-21 22:38:17.683 | WARNING | opentelemetry.sdk.metrics._internal.metric_reader_storage:_handle_view_instrument_match:280 - Views <opentelemetry.sdk.metrics._internal.view.View object at 0x7f8f8ee4fa50> and <opentelemetry.sdk.metrics._internal.view.View object at 0x7f8f8ee4fa50> will cause conflicting metrics identities
```
### Steps to Reproduce
```shell
- ENABLE_OTEL=true
- ENABLE_OTEL_METRICS=true
- ENABLE_OTEL_TRACES=true
- OTEL_EXPORTER_OTLP_PROTOCOL=grpc
- USE_OTEL_HTTP_EXPORTER=true
- OTEL_EXPORTER_OTLP_INSECURE=true # Use insecure connection for OTLP, remove in production
- OTEL_EXPORTER_OTLP_ENDPOINT=http://grafana-otel-lgtm:4317
- OTEL_SERVICE_NAME=open-webui
```
1. Start the container with the above environment variables
2. check the container logs using command docker logs open-webui
3. there is only one warning message as stated above when the open-webui application started
4. nothing else where there is no logs related to opentelemetry when doing chat w/ models on open-webui
### Logs & Screenshots
```shell
Loading WEBUI_SECRET_KEY from file, not provided as an environment variable.
Loading WEBUI_SECRET_KEY from .webui_secret_key
INFO [alembic.runtime.migration] Context impl SQLiteImpl.
INFO [alembic.runtime.migration] Will assume non-transactional DDL.
WARNI [open_webui.env] ⚠️ SECURITY WARNING: JWT_EXPIRES_IN is set to '-1'
See: https://docs.openwebui.com/getting-started/env-configuration
WARNI [open_webui.env]
WARNING: CORS_ALLOW_ORIGIN IS SET TO '*' - NOT RECOMMENDED FOR PRODUCTION DEPLOYMENTS.
/app/backend/open_webui/retrieval/vector/dbs/qdrant_multitenancy.py:77: UserWarning: Api key is used with an insecure connection.
else Qclient(
WARNI [langchain_community.utils.user_agent] USER_AGENT environment variable not set, consider setting it to identify your requests.
██████╗ ██████╗ ███████╗███╗ ██╗ ██╗ ██╗███████╗██████╗ ██╗ ██╗██╗
██╔═══██╗██╔══██╗██╔════╝████╗ ██║ ██║ ██║██╔════╝██╔══██╗██║ ██║██║
██║ ██║██████╔╝█████╗ ██╔██╗ ██║ ██║ █╗ ██║█████╗ ██████╔╝██║ ██║██║
██║ ██║██╔═══╝ ██╔══╝ ██║╚██╗██║ ██║███╗██║██╔══╝ ██╔══██╗██║ ██║██║
╚██████╔╝██║ ███████╗██║ ╚████║ ╚███╔███╔╝███████╗██████╔╝╚██████╔╝██║
╚═════╝ ╚═╝ ╚══════╝╚═╝ ╚═══╝ ╚══╝╚══╝ ╚══════╝╚═════╝ ╚═════╝ ╚═╝
v0.7.2 - building the best AI user interface.
https://github.com/open-webui/open-webui
Fetching 13 files: 100%|██████████| 13/13 [00:00<00:00, 160843.52it/s]
INFO: Started server process [1]
INFO: Waiting for application startup.
2026-01-21 22:38:16.746 | INFO | open_webui.utils.logger:start_logger:166 - GLOBAL_LOG_LEVEL: INFO
2026-01-21 22:38:16.746 | INFO | open_webui.main:lifespan:604 - Installing external dependencies of functions and tools...
2026-01-21 22:38:16.760 | INFO | open_webui.utils.plugin:install_frontmatter_requirements:286 - No requirements found in frontmatter.
2026-01-21 22:38:17.682 | INFO | uvicorn.protocols.http.httptools_impl:send:483 - 10.118.20.181:0 - "GET /ws/socket.io/?EIO=4&transport=polling&t=PlW_V8S HTTP/1.0" 200 - {"trace_id": "ff152a2a3de4d9663d662fee62743ad1", "span_id": "293c3abb49e926f3"}
2026-01-21 22:38:17.683 | WARNING | opentelemetry.sdk.metrics._internal.metric_reader_storage:_handle_view_instrument_match:280 - Views <opentelemetry.sdk.metrics._internal.view.View object at 0x7f8f8ee4fa50> and <opentelemetry.sdk.metrics._internal.view.View object at 0x7f8f8ee4fa50> will cause conflicting metrics identities
```
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-04-20 01:43:08 -05:00
#19136issue: tool servers don't work anymore in the latest version v0.6.36 by isNotOkay • Nov 12, 2025 • bug
#19063TTS not working in Open-WebUi by iSamPrime • Nov 09, 2025 • bug
💡Tips:
If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
If you found a solution in any of these issues, please share it here to help others
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
<!-- gh-comment-id:3778589231 -->
@owui-terminator[bot] commented on GitHub (Jan 21, 2026):
🔍 **Similar Issues Found**
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
1. [#20812](https://github.com/open-webui/open-webui/issues/20812) **issue: Unable to start Open WebUI on SaaS platforms (Render, Koyeb) after updating to v0.7.2**
*by tempppabx1 • Jan 20, 2026 • `bug`*
2. [#20327](https://github.com/open-webui/open-webui/issues/20327) **issue: Unable to use any Open WebUI version newer than 0.6.25 due to hybrid search performance**
*by galvanoid • Jan 02, 2026 • `bug`*
3. [#19496](https://github.com/open-webui/open-webui/issues/19496) **issue: 500 internal server error appears in v0.6.40**
*by cloudtuotuo • Nov 26, 2025 • `bug`*
4. [#14529](https://github.com/open-webui/open-webui/issues/14529) **issue: Open WebUI does not work on versions after version 0.6.7**
*by OpenSoftware-World • May 30, 2025 • `bug`*
5. [#19417](https://github.com/open-webui/open-webui/issues/19417) **issue: v0.6.37 SQL Error**
*by AKHYP • Nov 24, 2025 • `bug`*
<details>
<summary>Show 5 more related issues</summary>
6. [#18145](https://github.com/open-webui/open-webui/issues/18145) **issue: 0.6.33 regression**
*by Ark-Levy • Oct 08, 2025 • `bug`*
7. [#20128](https://github.com/open-webui/open-webui/issues/20128) **issue: Characters are broken in 0.6.43**
*by frenzybiscuit • Dec 22, 2025 • `bug`*
8. [#19755](https://github.com/open-webui/open-webui/issues/19755) **issue: Error: 404, message='Not Found', url='http://ollama:11434/api/embed'**
*by stevewillett • Dec 04, 2025 • `bug`*
9. [#19136](https://github.com/open-webui/open-webui/issues/19136) **issue: tool servers don't work anymore in the latest version v0.6.36**
*by isNotOkay • Nov 12, 2025 • `bug`*
10. [#19063](https://github.com/open-webui/open-webui/issues/19063) **TTS not working in Open-WebUi**
*by iSamPrime • Nov 09, 2025 • `bug`*
</details>
---
💡 **Tips:**
- If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
- If you found a solution in any of these issues, please share it here to help others
*This comment was generated automatically by a bot.* Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
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 @tnndclub on GitHub (Jan 21, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20840
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.7.2
Ollama Version (if applicable)
v0.14.2
Operating System
openSUSE Leap 16.0
Browser (if applicable)
Chrome 143.0.7499.193
Confirmation
README.md.Expected Behavior
With the ENABLE_OTEL set to true, both the traces and metrics should be sent to the configured endpoint following OTEL_EXPORTER_OTLP_ENDPOINT.
Actual Behavior
Neither traces nor metrics were sent to the configured endpoint.
The logs show a warning as below
Steps to Reproduce
Logs & Screenshots
Additional Information
No response
@owui-terminator[bot] commented on GitHub (Jan 21, 2026):
🔍 Similar Issues Found
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
#20812 issue: Unable to start Open WebUI on SaaS platforms (Render, Koyeb) after updating to v0.7.2
by tempppabx1 • Jan 20, 2026 •
bug#20327 issue: Unable to use any Open WebUI version newer than 0.6.25 due to hybrid search performance
by galvanoid • Jan 02, 2026 •
bug#19496 issue: 500 internal server error appears in v0.6.40
by cloudtuotuo • Nov 26, 2025 •
bug#14529 issue: Open WebUI does not work on versions after version 0.6.7
by OpenSoftware-World • May 30, 2025 •
bug#19417 issue: v0.6.37 SQL Error
by AKHYP • Nov 24, 2025 •
bugShow 5 more related issues
#18145 issue: 0.6.33 regression
by Ark-Levy • Oct 08, 2025 •
bug#20128 issue: Characters are broken in 0.6.43
by frenzybiscuit • Dec 22, 2025 •
bug#19755 issue: Error: 404, message='Not Found', url='http://ollama:11434/api/embed'
by stevewillett • Dec 04, 2025 •
bug#19136 issue: tool servers don't work anymore in the latest version v0.6.36
by isNotOkay • Nov 12, 2025 •
bug#19063 TTS not working in Open-WebUi
by iSamPrime • Nov 09, 2025 •
bug💡 Tips:
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.