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

dify textToAudio interface suddenly return null result,why? #16737

New Issue
Closed
opened 2026-02-21 19:27:23 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:27:23 -05:00
Owner
Copy Link
Copy Source

Originally created by @JaminVan on GitHub (Sep 4, 2025).

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

1.7.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image Image Previously, the text-to-speech interface on the platform was able to return the converted results. Is it now reaching the call frequency or call count limit?

✔️ Expected Behavior

The open source version of dify's text-to-speech interface can return the converted results.

❌ Actual Behavior

The open source version of dify's text-to-speech interface suddenly stops returning the converted result and instead returns null. The interface does not report an error. Has the interface call count been reached? The interface was previously usable.

Originally created by @JaminVan on GitHub (Sep 4, 2025). ### 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 1.7.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="1468" height="392" alt="Image" src="https://github.com/user-attachments/assets/7978f6ab-580a-4e30-aa07-1a59f79ca0f5" /> <img width="1099" height="364" alt="Image" src="https://github.com/user-attachments/assets/9f7a558c-523e-47a1-a130-97839aec16a1" /> Previously, the text-to-speech interface on the platform was able to return the converted results. Is it now reaching the call frequency or call count limit? ### ✔️ Expected Behavior The open source version of dify's text-to-speech interface can return the converted results. ### ❌ Actual Behavior The open source version of dify's text-to-speech interface suddenly stops returning the converted result and instead returns null. The interface does not report an error. Has the interface call count been reached? The interface was previously usable.
yindo added the 🐞 bug label 2026-02-21 19:27:23 -05:00
yindo closed this issue 2026-02-21 19:27:23 -05:00
yindo commented 2026-02-21 19:27:23 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 4, 2025):

Hi @JaminVan! I'm Dosu and I’m helping the dify team.

There are several known reasons why the text-to-speech (textToAudio) interface in Dify self-hosted Docker deployments can suddenly start returning null or empty results, even if it worked before:

  • The most common causes are missing or misconfigured FFmpeg dependencies, plugin daemon instability, resource constraints in Docker, network/API timeouts, or abrupt thread shutdowns. It's important to verify FFmpeg is installed inside your Docker container, check system resources, and monitor plugin daemon health and logs. Enabling debug logging in Dify can help pinpoint the issue. Also, make sure your TTS provider/model configuration is correct and the plugin daemon is up to date. See detailed troubleshooting steps here: Dify Issue #21893.

  • If the 'Voice' field is missing or not provided in your TTS request, the plugin daemon may reject the request or return null without an error. Some TTS providers require this field, even if the web UI doesn't mark it as mandatory. If you are using a custom plugin daemon, removing the 'required' validation rule for the 'Voice' field can be a workaround. More details: dify-official-plugins Issue #819.

  • Input text with special tags (like <think>...</think>) can sometimes cause TTS to fail or return empty audio. Try preprocessing or truncating the input text before sending it to TTS.

  • In some cases, the TTS result will only return if voice auto-play is enabled in your application settings. Make sure this is enabled if you rely on the tts_message API: Dify Issue #19361.

There are no documented call frequency or call count limits in the open-source/self-hosted version that would cause this behavior.

If none of these resolve the issue, check your backend logs for errors at the time of the null result and review your Docker/container resource usage.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Sep 4, 2025): <!-- Greeting --> Hi @JaminVan! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> There are several known reasons why the text-to-speech (textToAudio) interface in Dify self-hosted Docker deployments can suddenly start returning null or empty results, even if it worked before: - The most common causes are missing or misconfigured FFmpeg dependencies, plugin daemon instability, resource constraints in Docker, network/API timeouts, or abrupt thread shutdowns. It's important to verify FFmpeg is installed inside your Docker container, check system resources, and monitor plugin daemon health and logs. Enabling debug logging in Dify can help pinpoint the issue. Also, make sure your TTS provider/model configuration is correct and the plugin daemon is up to date. See detailed troubleshooting steps here: [Dify Issue #21893](https://github.com/langgenius/dify/issues/21893). - If the 'Voice' field is missing or not provided in your TTS request, the plugin daemon may reject the request or return null without an error. Some TTS providers require this field, even if the web UI doesn't mark it as mandatory. If you are using a custom plugin daemon, removing the 'required' validation rule for the 'Voice' field can be a workaround. More details: [dify-official-plugins Issue #819](https://github.com/langgenius/dify-official-plugins/issues/819). - Input text with special tags (like `<think>...</think>`) can sometimes cause TTS to fail or return empty audio. Try preprocessing or truncating the input text before sending it to TTS. - In some cases, the TTS result will only return if voice auto-play is enabled in your application settings. Make sure this is enabled if you rely on the tts_message API: [Dify Issue #19361](https://github.com/langgenius/dify/issues/19361). There are no documented call frequency or call count limits in the open-source/self-hosted version that would cause this behavior. If none of these resolve the issue, check your backend logs for errors at the time of the null result and review your Docker/container resource usage. <!-- 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/e2a1166d-be4a-4e0b-896b-2bc2691d218a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e2a1166d-be4a-4e0b-896b-2bc2691d218a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e2a1166d-be4a-4e0b-896b-2bc2691d218a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e2a1166d-be4a-4e0b-896b-2bc2691d218a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e2a1166d-be4a-4e0b-896b-2bc2691d218a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e2a1166d-be4a-4e0b-896b-2bc2691d218a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e2a1166d-be4a-4e0b-896b-2bc2691d218a?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&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/25149)
yindo commented 2026-02-21 19:27:23 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Sep 4, 2025):

From provided images, I can not infer what's happening as well.

@crazywoola commented on GitHub (Sep 4, 2025): From provided images, I can not infer what's happening as well.
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 🐞 bug
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#16737
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?