dify enterprise version Failed to transform tool message: PluginInvokeError: {\"args\":null,\"error_type\":\"PluginDaemonInnerError\",\"message\":\"failed to read response body: unexpected EOF\"}

[sunwenbo]

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

helm chart 3.0.0 ，dify-api 1.4.3

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

When playing long videos, if they exceed one minute, the workflow will report an error. To ensure stable reproduction, the configuration of nginx in the plugin has been adjusted

✔️ Expected Behavior

status code 200

❌ Actual Behavior

Failed to transform tool message: PluginInvokeError: {"args":null,"error_type":"PluginDaemonInnerError","message":"failed to read response body: unexpected EOF"}

[dosubot]

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

The "unexpected EOF" error during long video processing is most likely caused by infrastructure-level limits—specifically, Nginx proxy timeouts or body size restrictions. Dify streams plugin responses through Nginx, and if the response takes too long or is too large, Nginx or the HTTP layer may close the connection, resulting in this error. The code also enforces a 30MB per file and 8KB per chunk limit for plugin responses; exceeding these will cause failures as well reference.

To mitigate this, ensure your Nginx settings for proxy_read_timeout, proxy_send_timeout, keepalive_timeout, and client_max_body_size are set high enough for your use case. These are controlled by environment variables in the Dify Helm chart and referenced in the Nginx config templates reference. Double-check that all relevant Nginx instances (both in front of Dify and the plugin daemon) have these values set to at least 300s and a large enough body size.

If you have already maximized these settings and still see the error, check the Dify and plugin daemon logs for more details. There may be internal plugin timeouts or streaming issues, or the payload may be hitting the hard-coded chunk/file size limits in the code. If possible, try breaking up large payloads or optimizing the plugin to stream results more frequently.

Recent changes have improved error reporting for plugin invocation errors, so upgrading to the latest version may provide more actionable error messages reference.

To reply, just mention @dosu.

---

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

[crazywoola]

We do not provide technical support for starting from the source. Thank you for your understanding. We assume you have the necessary expertise to set it up independently. If you require technical support, please obtain our business license by contacting us at business@dify.ai.