Issue: Voice functionality is not working #5736

New Issue

2025-11-11T16:32:03-06:00

GiteaMirror commented

2025-11-11 16:32:03 -06:00

Originally created by @shentong0722 on GitHub (Jul 11, 2025).

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

v0.6.15

Ollama Version (if applicable)

No response

Operating System

Ubuntu 24.04 LTS

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 entire voice functionality is completely unusable

Actual Behavior

No matter which model or method is chosen, the following error occurs:

Steps to Reproduce

Completely unusable, all will appear on the above error message, even when using Deepgram

Logs & Screenshots

Additional Information

No response

Originally created by @shentong0722 on GitHub (Jul 11, 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 Docker ### Open WebUI Version v0.6.15 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu 24.04 LTS ### 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 entire voice functionality is completely unusable ### Actual Behavior No matter which model or method is chosen, the following error occurs: <img width="576" height="182" alt="Image" src="https://github.com/user-attachments/assets/c533bc42-6036-489b-9a51-d9c6c1d05bdb" /> ### Steps to Reproduce Completely unusable, all will appear on the above error message, even when using Deepgram ### Logs & Screenshots <img width="576" height="182" alt="Image" src="https://github.com/user-attachments/assets/2a2a0841-be56-4a65-bd10-7c9cdd67c385" /> ### Additional Information _No response_

GiteaMirror added the bug label 2025-11-11 16:32:03 -06:00

GiteaMirror closed this issue

2025-11-11 16:32:03 -06:00

GiteaMirror commented

2025-11-11 16:32:04 -06:00

@Stacktrace42 commented on GitHub (Jul 11, 2025):

I have the same issue, but it does seems to be something other than the deepgram integration:

Reproduction step:

setup deepgram and create a new api key
in settings, set deepgram as sst interation and provide api key
open a chat and try sst => error like shown above appears
Check deepgram logs => no entry, so no request has been sent out to deepgram
Reset the audio settings to:

6. open a chat and try stt again - same error message

@shentong0722: Can you confirm if this is also the case on your instance?

@Stacktrace42 commented on GitHub (Jul 11, 2025): I have the same issue, but it does seems to be something other than the deepgram integration: Reproduction step: 1. setup deepgram and create a new api key 2. in settings, set deepgram as sst interation and provide api key 3. open a chat and try sst => error like shown above appears 4. Check deepgram logs => no entry, so no request has been sent out to deepgram 5. Reset the audio settings to: <img width="1994" height="716" alt="Image" src="https://github.com/user-attachments/assets/7d55262c-555a-421b-a2e6-7b363f7ffefa" /> 6. open a chat and try stt again - same error message @shentong0722: Can you confirm if this is also the case on your instance?

GiteaMirror commented

2025-11-11 16:32:04 -06:00

@Qu4ndo commented on GitHub (Jul 11, 2025):

I don't know where I read about it ... but set the MIME Type to '*' and it probably will work. It's a bug which is fixed in one of the next stable releases or so.

@Qu4ndo commented on GitHub (Jul 11, 2025): I don't know where I read about it ... but set the MIME Type to '*' and it probably will work. It's a bug which is fixed in one of the next stable releases or so.

GiteaMirror commented

2025-11-11 16:32:04 -06:00