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

OpenAI Response Not Streaming #20007

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

Originally created by @trannluongg on GitHub (Oct 29, 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.1

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

I have a case, when using openai in dify, currently the data returned from AI, is not streamed like typing but returned in segments.

https://github.com/user-attachments/assets/dd05f0ca-1c95-47b8-8675-5d07b78c50ee

✔️ Expected Behavior

Streaming

❌ Actual Behavior

No response

Originally created by @trannluongg on GitHub (Oct 29, 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.1 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce I have a case, when using openai in dify, currently the data returned from AI, is not streamed like typing but returned in segments. https://github.com/user-attachments/assets/dd05f0ca-1c95-47b8-8675-5d07b78c50ee ### ✔️ Expected Behavior Streaming ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 20:05:22 -05:00
yindo closed this issue 2026-02-21 20:05:22 -05:00
yindo commented 2026-02-21 20:05:23 -05:00
Author
Owner
Copy Link
Copy Source

@trannluongg commented on GitHub (Oct 29, 2025):

@dosubot do you know where the error is?

@trannluongg commented on GitHub (Oct 29, 2025): @dosubot do you know where the error is?
yindo commented 2026-02-21 20:05:23 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 29, 2025):

The most common cause for OpenAI responses not streaming in self-hosted Dify is reverse proxy buffering—especially if you're using nginx. By default, nginx buffers responses, which breaks streaming. To fix this, add proxy_buffering off; to the relevant location block in your nginx config. Also, check for other network or proxy settings that might interfere with streaming responses. For more details and troubleshooting steps, see this discussion: nginx proxy buffering and streaming.

If you're not using nginx or have already disabled buffering, check that your backend is returning streaming responses in the correct Server-Sent Events (SSE) format: each chunk should start with data: (with a space), followed by a JSON object, and end with a double newline. Even a missing space after data: can break streaming in Dify and cause the UI to show no content, even if the backend logs look correct. More on this here: SSE format and debugging.

If everything looks correct but streaming still doesn't work, review your Dify backend logs for JSON parsing errors or "Non-JSON encountered" messages, which indicate a formatting issue in the streaming chunks.

There is also an open issue tracking this problem in v1.9.1, so it's a known limitation in the current version: OpenAI response not streaming issue.

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 (Oct 29, 2025): <!-- Answer --> The most common cause for OpenAI responses not streaming in self-hosted Dify is reverse proxy buffering—especially if you're using nginx. By default, nginx buffers responses, which breaks streaming. To fix this, add proxy_buffering off; to the relevant location block in your nginx config. Also, check for other network or proxy settings that might interfere with streaming responses. For more details and troubleshooting steps, see this discussion: [nginx proxy buffering and streaming](https://github.com/langgenius/dify/issues/26844). If you're not using nginx or have already disabled buffering, check that your backend is returning streaming responses in the correct Server-Sent Events (SSE) format: each chunk should start with data: (with a space), followed by a JSON object, and end with a double newline. Even a missing space after data: can break streaming in Dify and cause the UI to show no content, even if the backend logs look correct. More on this here: [SSE format and debugging](https://github.com/langgenius/dify/discussions/23229). If everything looks correct but streaming still doesn't work, review your Dify backend logs for JSON parsing errors or "Non-JSON encountered" messages, which indicate a formatting issue in the streaming chunks. There is also an open issue tracking this problem in v1.9.1, so it's a known limitation in the current version: [OpenAI response not streaming issue](https://github.com/langgenius/dify/issues/1542). <!-- 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/ea276d89-dbbb-45a9-9a9e-fee953e5043f?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ea276d89-dbbb-45a9-9a9e-fee953e5043f?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ea276d89-dbbb-45a9-9a9e-fee953e5043f?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ea276d89-dbbb-45a9-9a9e-fee953e5043f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ea276d89-dbbb-45a9-9a9e-fee953e5043f?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ea276d89-dbbb-45a9-9a9e-fee953e5043f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ea276d89-dbbb-45a9-9a9e-fee953e5043f?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/27606)
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#20007
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?