Originally created by @gongshaojie12 on GitHub (Jun 18, 2025).
Check Existing Issues
I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Pip Install
Open WebUI Version
0.6.15
Ollama Version (if applicable)
No response
Operating System
centos7.9
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
The newly added features are documented.
Actual Behavior
Custom Speech-to-Text Content-Type for Transcription: Define custom content types for audio transcription, ensuring compatibility with diverse audio sources and unlocking smoother, more accurate transcriptions in advanced setups.
LDAP Group Synchronization (Experimental): Automatically sync user groups from your LDAP directory directly into Open WebUI for seamless enterprise access management—simplifies identity integration and governance across your organization.
OpenTelemetry Metrics via OTLP Exporter (Experimental): Gain enterprise-grade analytics and monitor your AI usage in real time with experimental OpenTelemetry Metrics support—connect to any OTLP-compatible backend for instant insights into performance, load, and user interactions.
Among these three newly added features, why can't users be seen in the Open-WebUI backend interface after configuring the LDAP Group Synchronization feature?
I couldn't find any documentation or explanations for Custom Speech-to-Text Content-Type for Transcription and OpenTelemetry Metrics via OTLP Exporter (Experimental) , and there are no corresponding settings in the UI interface. Can you provide detailed step-by-step instructions for these features?
Steps to Reproduce
None
Logs & Screenshots
None
Additional Information
No response
Originally created by @gongshaojie12 on GitHub (Jun 18, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Pip Install
### Open WebUI Version
0.6.15
### Ollama Version (if applicable)
_No response_
### Operating System
centos7.9
### 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
The newly added features are documented.
### Actual Behavior
1. **Custom Speech-to-Text Content-Type for Transcription**: Define custom content types for audio transcription, ensuring compatibility with diverse audio sources and unlocking smoother, more accurate transcriptions in advanced setups.
2. **LDAP Group Synchronization (Experimental)**: Automatically sync user groups from your LDAP directory directly into Open WebUI for seamless enterprise access management—simplifies identity integration and governance across your organization.
3. **OpenTelemetry Metrics via OTLP Exporter (Experimental)**: Gain enterprise-grade analytics and monitor your AI usage in real time with experimental OpenTelemetry Metrics support—connect to any OTLP-compatible backend for instant insights into performance, load, and user interactions.
Among these three newly added features, why can't users be seen in the Open-WebUI backend interface after configuring the **LDAP Group Synchronization** feature?
I couldn't find any documentation or explanations for **Custom Speech-to-Text Content-Type for Transcription** and **OpenTelemetry Metrics via OTLP Exporter (Experimental)** , and there are no corresponding settings in the UI interface. Can you provide detailed step-by-step instructions for these features?
### Steps to Reproduce
None
### Logs & Screenshots
None
### Additional Information
_No response_
GiteaMirror
added the bug label 2025-11-11 16:25:06 -06:00
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 @gongshaojie12 on GitHub (Jun 18, 2025).
Check Existing Issues
Installation Method
Pip Install
Open WebUI Version
0.6.15
Ollama Version (if applicable)
No response
Operating System
centos7.9
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
The newly added features are documented.
Actual Behavior
Custom Speech-to-Text Content-Type for Transcription: Define custom content types for audio transcription, ensuring compatibility with diverse audio sources and unlocking smoother, more accurate transcriptions in advanced setups.
LDAP Group Synchronization (Experimental): Automatically sync user groups from your LDAP directory directly into Open WebUI for seamless enterprise access management—simplifies identity integration and governance across your organization.
OpenTelemetry Metrics via OTLP Exporter (Experimental): Gain enterprise-grade analytics and monitor your AI usage in real time with experimental OpenTelemetry Metrics support—connect to any OTLP-compatible backend for instant insights into performance, load, and user interactions.
Among these three newly added features, why can't users be seen in the Open-WebUI backend interface after configuring the LDAP Group Synchronization feature?
I couldn't find any documentation or explanations for Custom Speech-to-Text Content-Type for Transcription and OpenTelemetry Metrics via OTLP Exporter (Experimental) , and there are no corresponding settings in the UI interface. Can you provide detailed step-by-step instructions for these features?
Steps to Reproduce
None
Logs & Screenshots
None
Additional Information
No response
@tjbck commented on GitHub (Jun 18, 2025):
Added in as an env var, please check out our docs.