mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-05 18:38:17 -05:00
[GH-ISSUE #9227] STT API calls do not recognize or accept audio files. #15427
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#15427
Reference in New Issue
Block a user
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?
Originally created by @ckraushaar on GitHub (Feb 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/9227
Bug Report
Important Notes
Before submitting a bug report: Please check the Issues or Discussions section to see if a similar issue or feature request has already been posted. It's likely we're already tracking it! If you’re unsure, start a discussion post first. This will help us efficiently focus on improving the project.
Collaborate respectfully: We value a constructive attitude, so please be mindful of your communication. If negativity is part of your approach, our capacity to engage may be limited. We’re here to help if you’re open to learning and communicating positively. Remember, Open WebUI is a volunteer-driven project managed by a single maintainer and supported by contributors who also have full-time jobs. We appreciate your time and ask that you respect ours.
Contributing: If you encounter an issue, we highly encourage you to submit a pull request or fork the project. We actively work to prevent contributor burnout to maintain the quality and continuity of Open WebUI.
Bug reproducibility: If a bug cannot be reproduced with a
:mainor:devDocker setup, or a pip install with Python 3.11, it may require additional help from the community. In such cases, we will move it to the "issues" Discussions section due to our limited resources. We encourage the community to assist with these issues. Remember, it’s not that the issue doesn’t exist; we need your help!Note: Please remove the notes above when submitting your post. Thank you for your understanding and support!
Installation Method
Docker Installation
Environment
Open WebUI Version: v0.5.7
LocalAI: v2.25.0
Operating System: Rocky Linux 9.4
Browser (if applicable): [e.g., Chrome 100.0, Firefox 98.0]
Confirmation:
Expected Behavior:
Upload a webm, wav, mp3 file from curl cli command or php curl function and receive a JSON string of the transcribed text
Actual Behavior:
Returned JSON string when passing in an audio file:
{"detail":"Oops! It seems like the file format you're trying to upload is not supported. Please upload a file with a supported format (e.g., JPG, PNG, PDF, TXT) and try again."}
Description
Bug Summary:
When uploading an audio file using curl to the http://openwebui:port/api/v1/audio/transcriptions url it returns that the file is unrecognizable. I have tried .mp3, .wav and .webm, all with the same results.
Open WebUI website works for both TTS and STT calls using OpenAI settings directing to the local LocalAI Docker launched from the same docker-compose.yaml
I can pass the same file directly to LocalAI http://localai:port/v1/audio/transcriptions and receive the expected JSON string.
Appears to be an error on the file check when you receive a file over the api call. It seems it may only check for images or documents based on the error.
Reproduction Details
Steps to Reproduce:
ex: curl http://openwebui:port/api/v1/audio/transcriptions -H "Authorization: Bearer key" -H "Content-Type: multipart/form-data" -F file="@test.webm"
https://github.com/user-attachments/assets/3db60492-062d-4c2f-bde1-4057de42a8e6
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots/Screen Recordings (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!