langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

audio-to-text #21584

New Issue
Closed
opened 2026-02-21 20:13:18 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:13:18 -05:00
Owner
Copy Link
Copy Source

Originally created by @lantianliu5-alt on GitHub (Jan 12, 2026).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

"version": "1.11.2",

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

{
"code": "invalid_param",
"message": "Speech to text is not enabled",
"status": 400
}

✔️ Expected Behavior

I hope to offer a solution. I said to run it locally with Docker.

❌ Actual Behavior

No response

Originally created by @lantianliu5-alt on GitHub (Jan 12, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version "version": "1.11.2", ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce { "code": "invalid_param", "message": "Speech to text is not enabled", "status": 400 } ### ✔️ Expected Behavior I hope to offer a solution. I said to run it locally with Docker. ### ❌ Actual Behavior _No response_
yindo added the 🙋‍♂️ question🌚 invalid labels 2026-02-21 20:13:18 -05:00
yindo closed this issue 2026-02-21 20:13:19 -05:00
yindo commented 2026-02-21 20:13:19 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 12, 2026):

Hi @lantianliu5-alt! I'm Dosu and I’m helping the dify team.

The "Speech to text is not enabled" error in Dify (self-hosted, Docker, v1.11.2) happens when the speech-to-text feature isn't enabled in your app's Function settings, or when no speech-to-text provider/model is configured for your tenant. This isn't controlled by an environment variable or Docker setting, but by feature flags and provider configuration in the UI and database.

To enable speech-to-text:

  1. In your app's Function settings, turn on the speech-to-text feature.
  2. Publish the app after enabling the feature—voice features only work after publishing, not in preview mode.
  3. Start a new conversation (existing chats won't activate new settings).
  4. In the system provider settings, make sure you have a speech-to-text (STT) model/provider configured and set as default for your tenant.
  5. Make sure required dependencies (like FFmpeg) and provider credentials (API keys, etc.) are set up in your Docker environment.

If any of these steps are missed, you'll get the "Speech to text is not enabled" error when calling the audio-to-text endpoint. There is no standalone speech-to-text plugin in 1.11.2; it's managed through core settings and provider configuration. For more details, see the relevant issue discussion and code references.

Checklist:

  • Speech-to-text enabled in app Function settings
  • App published after enabling
  • New conversation started
  • STT provider/model configured in system settings
  • Dependencies and credentials set up in Docker

If you follow these steps and still see the error, double-check your provider/model configuration and that you're not in preview mode.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 12, 2026): <!-- Greeting --> Hi @lantianliu5-alt! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The "Speech to text is not enabled" error in Dify (self-hosted, Docker, v1.11.2) happens when the speech-to-text feature isn't enabled in your app's Function settings, or when no speech-to-text provider/model is configured for your tenant. This isn't controlled by an environment variable or Docker setting, but by feature flags and provider configuration in the UI and database. To enable speech-to-text: 1. In your app's Function settings, turn on the speech-to-text feature. 2. Publish the app after enabling the feature—voice features only work after publishing, not in preview mode. 3. Start a new conversation (existing chats won't activate new settings). 4. In the system provider settings, make sure you have a speech-to-text (STT) model/provider configured and set as default for your tenant. 5. Make sure required dependencies (like FFmpeg) and provider credentials (API keys, etc.) are set up in your Docker environment. If any of these steps are missed, you'll get the "Speech to text is not enabled" error when calling the audio-to-text endpoint. There is no standalone speech-to-text plugin in 1.11.2; it's managed through core settings and provider configuration. For more details, see the relevant [issue discussion](https://github.com/langgenius/dify/issues/16758#issuecomment-2750790035) and [code references](https://github.com/langgenius/dify/blob/b63dfbf654ed2191aa94aa4bcf8d09c09cc90759/api/services/audio_service.py#L31-L73). Checklist: - [ ] Speech-to-text enabled in app Function settings - [ ] App published after enabling - [ ] New conversation started - [ ] STT provider/model configured in system settings - [ ] Dependencies and credentials set up in Docker If you follow these steps and still see the error, double-check your provider/model configuration and that you're not in preview mode. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/ed6cd628-75e8-4866-b3f6-8be3c861640f?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ed6cd628-75e8-4866-b3f6-8be3c861640f?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ed6cd628-75e8-4866-b3f6-8be3c861640f?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ed6cd628-75e8-4866-b3f6-8be3c861640f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ed6cd628-75e8-4866-b3f6-8be3c861640f?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ed6cd628-75e8-4866-b3f6-8be3c861640f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ed6cd628-75e8-4866-b3f6-8be3c861640f?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20%22Speech%20to%20text%20is%20not%20enabled%22%20error%20in%20Dify%20%28self-hosted%2C%20Docker%2C%20v1.11.2%29%20happens%20when%20the%20speech-to-text%20feature%20isn%27t%20enabled%20in%20your%20app%27s%20Function%20settings%2C%20or%20when%20no%20speech-to-text%20provider/model%20is%20configured%20for%20your%20tenant.%20This%20isn%27t%20controlled%20by%20an%20environment%20variable%20or%20Docker%20setting%2C%20but%20by%20feature%20flags%20and%20provider%20configuration%20in%20the%20UI%20and%20database.%0A%0ATo%20enable%20speech-to-text%3A%0A%0A1.%20In%20your%20app%27s%20Function%20settings%2C%20turn%20on%20the%20speech-to-text%20feature.%0A2.%20Publish%20the%20app%20after%20enabling%20the%20feature%E2%80%94voice%20features%20only%20work%20after%20publishing%2C%20not%20in%20preview%20mode.%0A3.%20Start%20a%20new%20conversation%20%28existing%20chats%20won%27t%20activate%20new%20settings%29.%0A4.%20In%20the%20system%20provider%20settings%2C%20make%20sure%20you%20have%20a%20speech-to-text%20%28STT%29%20model/provider%20configured%20and%20set%20as%20default%20for%20your%20tenant.%0A5.%20Make%20sure%20required%20dependencies%20%28like%20FFmpeg%29%20and%20provider%20credentials%20%28API%20keys%2C%20etc.%29%20are%20set%20up%20in%20your%20Docker%20environment.%0A%0AIf%20any%20of%20these%20steps%20are%20missed%2C%20you%27ll%20get%20the%20%22Speech%20to%20text%20is%20not%20enabled%22%20error%20when%20calling%20the%20audio-to-text%20endpoint.%20There%20is%20no%20standalone%20speech-to-text%20plugin%20in%201.11.2%3B%20it%27s%20managed%20through%20core%20settings%20and%20provider%20configuration.%20For%20more%20details%2C%20see%20the%20relevant%20%5Bissue%20discussion%5D%28https%3A//github.com/langgenius/dify/issues/16758%23issuecomment-2750790035%29%20and%20%5Bcode%20references%5D%28https%3A//github.com/langgenius/dify/blob/b63dfbf654ed2191aa94aa4bcf8d09c09cc90759/api/services/audio_service.py%23L31-L73%29.%0A%0AChecklist%3A%0A-%20%5B%20%5D%20Speech-to-text%20enabled%20in%20app%20Function%20settings%0A-%20%5B%20%5D%20App%20published%20after%20enabling%0A-%20%5B%20%5D%20New%20conversation%20started%0A-%20%5B%20%5D%20STT%20provider/model%20configured%20in%20system%20settings%0A-%20%5B%20%5D%20Dependencies%20and%20credentials%20set%20up%20in%20Docker%0A%0AIf%20you%20follow%20these%20steps%20and%20still%20see%20the%20error%2C%20double-check%20your%20provider/model%20configuration%20and%20that%20you%27re%20not%20in%20preview%20mode.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/30856)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🌚 invalid 🙋‍♂️ question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#21584
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?