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

pro订阅下请求接口异常 #14732

New Issue
Closed
opened 2026-02-21 19:18:33 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 19:18:33 -05:00
Owner
Copy Link
Copy Source

Originally created by @shaoqing404 on GitHub (Jun 19, 2025).

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.4.3 官方版本

Cloud or Self Hosted

Cloud

Steps to reproduce

pro订阅下

调用任意api请求，存在65/100 的调用错误，模型请求的开销被正常扣除。

该问题近期频发。

这可能是一个紧急bug，在北京时间6月19日11时以后频发，请关注。

✔️ Expected Behavior

No response

❌ Actual Behavior

[openai] Error: PluginInvokeError: {"args":null,"error_type":"PluginDaemonInnerError","message":"Error sending request to aws lambda: Post "http://plugin-runtime-internal.dify.ai/******************/invoke?action=invoke_llm": read tcp 10.10.25.26:44248-\u003e10.10.44.80:80: read: connection timed out"}

[openai] Error: PluginInvokeError: {"args":null,"error_type":"PluginDaemonInnerError","message":"Error sending request to aws lambda: Post "http://plugin-runtime-internal.dify.ai/******************************/invoke?action=invoke_llm": read tcp 10.10.25.26:44248-\u003e10.10.44.80:80: read: connection timed out"}

Originally created by @shaoqing404 on GitHub (Jun 19, 2025). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.4.3 官方版本 ### Cloud or Self Hosted Cloud ### Steps to reproduce pro订阅下 调用任意api请求，存在65/100 的调用错误，模型请求的开销被正常扣除。 该问题近期频发。 这可能是一个紧急bug，在北京时间6月19日11时以后频发，请关注。 ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior [openai] Error: PluginInvokeError: {"args":null,"error_type":"PluginDaemonInnerError","message":"Error sending request to aws lambda: Post \"http://plugin-runtime-internal.dify.ai/******************/invoke?action=invoke_llm\": read tcp 10.10.25.26:44248-\u003e10.10.44.80:80: read: connection timed out"} [openai] Error: PluginInvokeError: {"args":null,"error_type":"PluginDaemonInnerError","message":"Error sending request to aws lambda: Post \"http://plugin-runtime-internal.dify.ai/******************************/invoke?action=invoke_llm\": read tcp 10.10.25.26:44248-\u003e10.10.44.80:80: read: connection timed out"}
yindo added the 🐞 bugcloud labels 2026-02-21 19:18:33 -05:00
yindo closed this issue 2026-02-21 19:18:33 -05:00
yindo commented 2026-02-21 19:18:33 -05:00
Author
Owner
Copy Link
Copy Source

@shaoqing404 commented on GitHub (Jun 19, 2025):

同时还见：[openai] Error: PluginInvokeError: {"args":null,"error_type":"PluginDaemonInnerError","message":"encountered an error: invalid character '\u003c' looking for beginning of value status: 504 Gateway Time-out original response: \u003chtml\u003e"}

该问题是导致api长时间报错的关键问题之一，站报错占比约60%，我所在的位置是加州，尝试从中国上海、西雅图、日本的节点进行请求，问题均存在。

@shaoqing404 commented on GitHub (Jun 19, 2025): 同时还见：[openai] Error: PluginInvokeError: {"args":null,"error_type":"PluginDaemonInnerError","message":"encountered an error: invalid character '\u003c' looking for beginning of value status: 504 Gateway Time-out original response: \u003chtml\u003e"} 该问题是导致api长时间报错的关键问题之一，站报错占比约60%，我所在的位置是加州，尝试从中国上海、西雅图、日本的节点进行请求，问题均存在。
yindo commented 2026-02-21 19:18:33 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jun 19, 2025):

[FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)

For pro users, please report bug through email.

@crazywoola commented on GitHub (Jun 19, 2025): [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) For pro users, please report bug through email.
yindo commented 2026-02-21 19:18:33 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 19, 2025):

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

The error with "invalid character '<' looking for beginning of value status: 504 Gateway Time-out" means the backend is returning an HTML error page (often from a proxy or gateway) instead of the expected JSON, usually because the plugin daemon or AWS Lambda didn't respond in time. This is almost always an infrastructure or network bottleneck, not a code bug.

Recent investigations and code reviews show that Dify's plugin invocation relies on HTTP requests to the plugin daemon, and timeouts or 504 errors are surfaced directly if the downstream service is slow or overloaded. There are no recent code changes that would cause this, but there have been performance bottlenecks reported when large prompt messages are transmitted repeatedly between services, especially after the plugin-daemon was separated from the backend. This can lead to excessive payloads and timeouts in multi-turn or high-load scenarios, and a fix was recently applied to remove redundant prompt messages from responses, but it may not cover all cases yet (source, source).

Rate limiting is enforced at the Redis level, but if the infrastructure (plugin daemon, AWS Lambda, or network) is overloaded or misconfigured, users will see these timeouts regardless of rate limit settings (source).

This issue is not specific to your location—users in multiple regions are affected, which points to a backend or infra-wide bottleneck. The most actionable steps are to check for recent infra changes (like plugin storage config, network/proxy timeouts, or plugin daemon resource limits), monitor plugin daemon and Lambda logs for slowdowns, and ensure the latest plugin-daemon fixes are deployed (source, source).

If you have access to infra settings, try increasing timeouts and resource limits for the plugin daemon and check for any recent changes in storage or proxy configuration. If you are not managing the infra, this will need to be escalated to the platform provider.

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Jun 19, 2025): <!-- Greeting --> Hi @shaoqing404! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The error with "invalid character '<' looking for beginning of value status: 504 Gateway Time-out" means the backend is returning an HTML error page (often from a proxy or gateway) instead of the expected JSON, usually because the plugin daemon or AWS Lambda didn't respond in time. This is almost always an infrastructure or network bottleneck, not a code bug. Recent investigations and code reviews show that Dify's plugin invocation relies on HTTP requests to the plugin daemon, and timeouts or 504 errors are surfaced directly if the downstream service is slow or overloaded. There are no recent code changes that would cause this, but there have been performance bottlenecks reported when large prompt messages are transmitted repeatedly between services, especially after the plugin-daemon was separated from the backend. This can lead to excessive payloads and timeouts in multi-turn or high-load scenarios, and a fix was recently applied to remove redundant prompt messages from responses, but it may not cover all cases yet ([source](https://github.com/langgenius/dify/issues/19467), [source](https://github.com/langgenius/dify/pull/20391)). Rate limiting is enforced at the Redis level, but if the infrastructure (plugin daemon, AWS Lambda, or network) is overloaded or misconfigured, users will see these timeouts regardless of rate limit settings ([source](https://github.com/langgenius/dify/blob/8f64327d57967a9235695defa44dc8e259da4b78/api/core/app/features/rate_limiting/rate_limit.py)). This issue is not specific to your location—users in multiple regions are affected, which points to a backend or infra-wide bottleneck. The most actionable steps are to check for recent infra changes (like plugin storage config, network/proxy timeouts, or plugin daemon resource limits), monitor plugin daemon and Lambda logs for slowdowns, and ensure the latest plugin-daemon fixes are deployed ([source](https://github.com/langgenius/dify/pull/20613), [source](https://github.com/langgenius/dify/pull/20903)). If you have access to infra settings, try increasing timeouts and resource limits for the plugin daemon and check for any recent changes in storage or proxy configuration. If you are not managing the infra, this will need to be escalated to the platform provider. <!-- 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/685eef1e-a772-4038-a089-c32d0330db8f?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/685eef1e-a772-4038-a089-c32d0330db8f?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/685eef1e-a772-4038-a089-c32d0330db8f?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/685eef1e-a772-4038-a089-c32d0330db8f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/685eef1e-a772-4038-a089-c32d0330db8f?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/685eef1e-a772-4038-a089-c32d0330db8f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/685eef1e-a772-4038-a089-c32d0330db8f?feedback_type=other)</sup>&nbsp;&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/21233)
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 cloud 🐞 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#14732
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?