[azure_openai] Error: peer closed connection without sending complete message body (incomplete chunked read)

langgenius / dify

Dify is an open-source LLM app development platform. Dify's intuitive interface combines AI workflow, RAG pipeline, agent capabilities, model management, observability features and more, letting you quickly go from prototype to production.

Other

49.72k stars 7.11k forks source link

Self Checks

[X] This is only for bug report, if you would like to ask a question, please head to Discussions.
[X] I have searched for existing issues search for existing issues, including closed ones.
[X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
[X] Please do not modify this template :) and fill in all the required fields.

Dify version

0.9.2

Cloud or Self Hosted

Self Hosted (Docker), Self Hosted (Source)

Steps to reproduce

When my project code requests the chat-messages interface twice in a row and sends pictures, the interface returns [azure_openai] Error: peer closed connection without sending complete message body (incomplete chunked read)

✔️ Expected Behavior

Normal return

❌ Actual Behavior

No response

Hey @zhai5191! 👋 I'm here to help you with any bugs, questions, or contributions you have regarding Dify. I'll do my best to assist you while we wait for a human maintainer.

I couldn't find a specific solution to the "peer closed connection without sending complete message body" error in the Dify repository. However, there are a few similar discussions that might be relevant:

Connection error: request error, status_code: 503 - This discussion is still open and might provide insights into connection-related issues.
When using a chatbot with Gemini 1.5 Flush as a model, an error occurs from the second post with the same conversation ID - This is another open discussion that deals with errors occurring on consecutive requests, which might be similar to your issue.
When publishing Api, '/chat-messages' api responds slowly with data in streaming mode - This discussion is also open and might offer some context on performance issues with the chat-messages API.

These discussions might not directly solve your problem but could provide some context or potential workarounds.

To continue talking to Dosu, mention @dosu.

langgenius / dify