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

TTS preview loading #20142

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

Originally created by @protectedMan on GitHub (Nov 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.9.0

Cloud or Self Hosted

Cloud

Steps to reproduce

The system model has been configured with the TTS model, but it gets stuck and produces no sound when the TTS is used?

Image Image

✔️ Expected Behavior

TTS is working normally

❌ Actual Behavior

The system model has been configured with the TTS model, but it gets stuck and produces no sound when the TTS is used?

Originally created by @protectedMan on GitHub (Nov 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.9.0 ### Cloud or Self Hosted Cloud ### Steps to reproduce The system model has been configured with the TTS model, but it gets stuck and produces no sound when the TTS is used? <img width="1740" height="652" alt="Image" src="https://github.com/user-attachments/assets/4248e9b2-9ab7-4e99-a633-144fd925c836" /> <img width="698" height="1172" alt="Image" src="https://github.com/user-attachments/assets/69122d66-db17-463c-b6ce-1080faf6bf04" /> ### ✔️ Expected Behavior TTS is working normally ### ❌ Actual Behavior The system model has been configured with the TTS model, but it gets stuck and produces no sound when the TTS is used?
yindo added the 🐞 bug label 2026-02-21 20:06:02 -05:00
yindo closed this issue 2026-02-21 20:06:02 -05:00
yindo commented 2026-02-21 20:06:02 -05:00
Author
Owner
Copy Link
Copy Source

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

This TTS issue in Dify self-hosted Docker setups is a known pain point. The most common causes are missing FFmpeg (required for TTS audio processing), unsupported audio formats (TTS output must be mp3), or misconfiguration in the workflow/app (TTS must be enabled and the workflow published) [source]source]source]. Some TTS models (like Kokoro) also do not support stream mode, which can cause the system to hang if used [source].

A recent code fix (merged after v1.9.0) removed unnecessary Flask context preservation in the audio service, which could cause TTS to hang or fail silently in some cases [source]. If you are on v1.9.0, consider updating to the latest version to benefit from this and other TTS-related fixes.

Troubleshooting checklist:

  • Make sure FFmpeg is installed and available in your Docker environment.
  • Confirm your TTS model outputs mp3 audio.
  • Double-check that TTS is enabled in your workflow/app and that the workflow is published.
  • If using custom or third-party TTS models, verify they support stream mode.
  • Check your Docker environment variables and port mappings to ensure external access to audio/file URLs [source].

If the problem persists after these steps and updating, check your logs for errors and share them for deeper diagnosis.

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 (Nov 4, 2025): <!-- Answer --> This TTS issue in Dify self-hosted Docker setups is a known pain point. The most common causes are missing FFmpeg (required for TTS audio processing), unsupported audio formats (TTS output must be mp3), or misconfiguration in the workflow/app (TTS must be enabled and the workflow published) [[source](https://github.com/langgenius/dify/issues/17919)][source](https://github.com/langgenius/dify/issues/19742)][source](https://github.com/langgenius/dify/issues/15910)]. Some TTS models (like Kokoro) also do not support stream mode, which can cause the system to hang if used [[source](https://github.com/langgenius/dify/issues/17183)]. A recent code fix (merged after v1.9.0) removed unnecessary Flask context preservation in the audio service, which could cause TTS to hang or fail silently in some cases [[source](https://github.com/langgenius/dify/pull/27380)]. If you are on v1.9.0, consider updating to the latest version to benefit from this and other TTS-related fixes. Troubleshooting checklist: - Make sure FFmpeg is installed and available in your Docker environment. - Confirm your TTS model outputs mp3 audio. - Double-check that TTS is enabled in your workflow/app and that the workflow is published. - If using custom or third-party TTS models, verify they support stream mode. - Check your Docker environment variables and port mappings to ensure external access to audio/file URLs [[source](https://github.com/langgenius/dify-docs/issues/471#issuecomment-3343690952)]. If the problem persists after these steps and updating, check your logs for errors and share them for deeper diagnosis. <!-- 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/8303ff30-6882-478c-9a9e-f1896b982a26?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/8303ff30-6882-478c-9a9e-f1896b982a26?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/8303ff30-6882-478c-9a9e-f1896b982a26?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/8303ff30-6882-478c-9a9e-f1896b982a26?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/8303ff30-6882-478c-9a9e-f1896b982a26?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/8303ff30-6882-478c-9a9e-f1896b982a26?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/8303ff30-6882-478c-9a9e-f1896b982a26?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/27848)
yindo commented 2026-02-21 20:06:02 -05:00
Author
Owner
Copy Link
Copy Source

@protectedMan commented on GitHub (Nov 4, 2025):

This TTS issue in Dify self-hosted Docker setups is a known pain point. The most common causes are missing FFmpeg (required for TTS audio processing), unsupported audio formats (TTS output must be mp3), or misconfiguration in the workflow/app (TTS must be enabled and the workflow published) [source]source]source]. Some TTS models (like Kokoro) also do not support stream mode, which can cause the system to hang if used [source].

A recent code fix (merged after v1.9.0) removed unnecessary Flask context preservation in the audio service, which could cause TTS to hang or fail silently in some cases [source]. If you are on v1.9.0, consider updating to the latest version to benefit from this and other TTS-related fixes.

Troubleshooting checklist:

  • Make sure FFmpeg is installed and available in your Docker environment.
  • Confirm your TTS model outputs mp3 audio.
  • Double-check that TTS is enabled in your workflow/app and that the workflow is published.
  • If using custom or third-party TTS models, verify they support stream mode.
  • Check your Docker environment variables and port mappings to ensure external access to audio/file URLs [source].

If the problem persists after these steps and updating, check your logs for errors and share them for deeper diagnosis.

To reply, just mention @dosu.

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

I tried the latest version of dify cloud and encountered the same issue

@protectedMan commented on GitHub (Nov 4, 2025): > This TTS issue in Dify self-hosted Docker setups is a known pain point. The most common causes are missing FFmpeg (required for TTS audio processing), unsupported audio formats (TTS output must be mp3), or misconfiguration in the workflow/app (TTS must be enabled and the workflow published) [[source](https://github.com/langgenius/dify/issues/17919)][source](https://github.com/langgenius/dify/issues/19742)][source](https://github.com/langgenius/dify/issues/15910)]. Some TTS models (like Kokoro) also do not support stream mode, which can cause the system to hang if used [[source](https://github.com/langgenius/dify/issues/17183)]. > > A recent code fix (merged after v1.9.0) removed unnecessary Flask context preservation in the audio service, which could cause TTS to hang or fail silently in some cases [[source](https://github.com/langgenius/dify/pull/27380)]. If you are on v1.9.0, consider updating to the latest version to benefit from this and other TTS-related fixes. > > Troubleshooting checklist: > > * Make sure FFmpeg is installed and available in your Docker environment. > * Confirm your TTS model outputs mp3 audio. > * Double-check that TTS is enabled in your workflow/app and that the workflow is published. > * If using custom or third-party TTS models, verify they support stream mode. > * Check your Docker environment variables and port mappings to ensure external access to audio/file URLs [[source](https://github.com/langgenius/dify-docs/issues/471#issuecomment-3343690952)]. > > If the problem persists after these steps and updating, check your logs for errors and share them for deeper diagnosis. > > _To reply, just mention [@dosu](https://go.dosu.dev/dosubot)._ > > How did I do? [Good](https://app.dosu.dev/response-feedback/8303ff30-6882-478c-9a9e-f1896b982a26?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/8303ff30-6882-478c-9a9e-f1896b982a26?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/8303ff30-6882-478c-9a9e-f1896b982a26?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/8303ff30-6882-478c-9a9e-f1896b982a26?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/8303ff30-6882-478c-9a9e-f1896b982a26?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/8303ff30-6882-478c-9a9e-f1896b982a26?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/8303ff30-6882-478c-9a9e-f1896b982a26?feedback_type=other)  [![Chat with Dosu](https://camo.githubusercontent.com/d9ffebb979729c9ef0fc4e3090dbae5b17cabbfec8afe378ada6b81913d6ad8a/68747470733a2f2f646f73752e6465762f646f73752d636861742d62616467652e737667)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github) [![Join Discord](https://camo.githubusercontent.com/d562c2df5e4567ea41d37f1d91a4da0839d8341037045b103b2da268998de17f/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f6a6f696e2d3538363546323f6c6f676f3d646973636f7264266c6f676f436f6c6f723d7768697465266c6162656c3d)](https://go.dosu.dev/discord-bot) [![Share on X](https://camo.githubusercontent.com/4649f705e2396d6f328dbc8e800a0509c9c17b3b20253b36706c393df124b93d/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f582d73686172652d626c61636b)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/27848) I tried the latest version of dify cloud and encountered the same issue
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#20142
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?