mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 19:08:59 -05:00
[GH-ISSUE #22997] bug: Admin Audio Settings - STT/TTS engine dropdowns missing backend-supported options (v0.8.10) #58528
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 @95256155o on GitHub (Mar 24, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22997
Describe the bug
In Admin Panel → Settings → Audio, both STT and TTS engine dropdowns are missing most backend-supported options:
Default,Web APIDefault,Kokoro.js (Browser)Backend router (
audio.py) supportsopenai,azure,deepgram,mistralfor STT andopenai,azure,elevenlabsfor TTS — none of these appear in the UI.This is confirmed as a frontend-only issue: after manually writing
audio.stt.engine=openai+ API key directly into theconfigtable inwebui.db, OpenAI Whisper transcription works perfectly (backend logs showPOST /api/v1/audio/transcriptions→ 200). The dropdown still does not reflect the active engine.Steps to reproduce
docker run -d --name open-webui -p 4319:8080 -v open-webui-data:/app/backend/data ghcr.io/open-webui/open-webui:mainExpected behavior
Dropdowns should list all engines supported by the backend: OpenAI, Azure, Deepgram, Mistral (STT) and OpenAI, Azure, ElevenLabs (TTS).
Workaround
Directly insert config into
webui.db:Then restart container. Backend works; UI still shows wrong engine name.
Environment
ghcr.io/open-webui/open-webui:mainsha256:b80a96e14bb15ea79aec96fbdad4aeab6b3ee7b61520d83b5dbc8c4f47d433a9@95256155o commented on GitHub (Mar 24, 2026):
Closing to re-submit using the proper bug report template. Apologies for the noise.