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

Server encountering internal error and unable to complete requests. #21061

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

Originally created by @Kronkmeister on GitHub (Dec 15, 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.11.1

Cloud or Self Hosted

Cloud

Steps to reproduce

Making a request by sending a message to an agent in the Debug window.

✔️ Expected Behavior

Expecting a response by agent. Worked for the last weeks until a few hours ago.

❌ Actual Behavior

Any request results in the same error message: "The server encountered an internal error and was unable to complete your request. Either that server is overloaded or there is an error in the application."

No response by the agent. Same issue for any deployed agent or workflow.

Image
Originally created by @Kronkmeister on GitHub (Dec 15, 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.11.1 ### Cloud or Self Hosted Cloud ### Steps to reproduce Making a request by sending a message to an agent in the Debug window. ### ✔️ Expected Behavior Expecting a response by agent. Worked for the last weeks until a few hours ago. ### ❌ Actual Behavior Any request results in the same error message: "The server encountered an internal error and was unable to complete your request. Either that server is overloaded or there is an error in the application." No response by the agent. Same issue for any deployed agent or workflow. <img width="579" height="583" alt="Image" src="https://github.com/user-attachments/assets/4ba955df-c926-4c66-a4d7-fb9b4b986627" />
yindo added the 🐞 bugcloud labels 2026-02-21 20:10:30 -05:00
yindo closed this issue 2026-02-21 20:10:30 -05:00
yindo commented 2026-02-21 20:10:30 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 15, 2025):

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

The most common causes for internal server errors like this in Dify Cloud are model provider misconfigurations, plugin errors, or backend/database issues. Here are some steps you can try in the Dify Cloud UI:

  • Check your Model Providers settings for any invalid or duplicate providers. Remove and re-add them if needed, and make sure provider names match the expected format (e.g., azure_openai or langgenius/azure_openai, not with two slashes) [source].
  • Review your plugin configurations. Outdated plugins or missing expected keys in plugin/tool responses can cause 500 errors in agent workflows. Try upgrading plugins and ensure your workflow logic handles missing keys defensively [source].
  • Test with a simple agent or workflow to see if the error persists. If it does, it may indicate a system-wide backend issue.

Since you’re on the cloud version and don’t have access to backend logs, if the problem affects all agents and workflows and persists after checking the above, it’s likely a backend or infrastructure issue on the Dify Cloud side. In this case, gather as much detail as possible (steps to reproduce, error messages, affected agents/workflows, and any recent changes) and escalate to Dify Cloud support for further investigation [source].

If you notice any recent changes in your workspace (like new model providers, plugin updates, or workflow edits), try reverting those to see if the issue resolves. If you see a pattern (e.g., only certain plugins or models trigger the error), that info will help narrow down the root cause.

To reply, just mention @dosu.

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

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Dec 15, 2025): <!-- Greeting --> Hi @Kronkmeister! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The most common causes for internal server errors like this in Dify Cloud are model provider misconfigurations, plugin errors, or backend/database issues. Here are some steps you can try in the Dify Cloud UI: - Check your Model Providers settings for any invalid or duplicate providers. Remove and re-add them if needed, and make sure provider names match the expected format (e.g., `azure_openai` or `langgenius/azure_openai`, not with two slashes) [[source]](https://github.com/langgenius/dify/issues/25775). - Review your plugin configurations. Outdated plugins or missing expected keys in plugin/tool responses can cause 500 errors in agent workflows. Try upgrading plugins and ensure your workflow logic handles missing keys defensively [[source]](https://github.com/langgenius/dify-official-plugins/issues/1706). - Test with a simple agent or workflow to see if the error persists. If it does, it may indicate a system-wide backend issue. Since you’re on the cloud version and don’t have access to backend logs, if the problem affects all agents and workflows and persists after checking the above, it’s likely a backend or infrastructure issue on the Dify Cloud side. In this case, gather as much detail as possible (steps to reproduce, error messages, affected agents/workflows, and any recent changes) and escalate to Dify Cloud support for further investigation [[source]](https://github.com/langgenius/dify/issues/20306). If you notice any recent changes in your workspace (like new model providers, plugin updates, or workflow edits), try reverting those to see if the issue resolves. If you see a pattern (e.g., only certain plugins or models trigger the error), that info will help narrow down the root cause. <!-- 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/4a52b21d-1562-438a-9da1-10433dba339f?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/4a52b21d-1562-438a-9da1-10433dba339f?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/4a52b21d-1562-438a-9da1-10433dba339f?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/4a52b21d-1562-438a-9da1-10433dba339f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/4a52b21d-1562-438a-9da1-10433dba339f?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/4a52b21d-1562-438a-9da1-10433dba339f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/4a52b21d-1562-438a-9da1-10433dba339f?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20most%20common%20causes%20for%20internal%20server%20errors%20like%20this%20in%20Dify%20Cloud%20are%20model%20provider%20misconfigurations%2C%20plugin%20errors%2C%20or%20backend/database%20issues.%20Here%20are%20some%20steps%20you%20can%20try%20in%20the%20Dify%20Cloud%20UI%3A%0A%0A-%20Check%20your%20Model%20Providers%20settings%20for%20any%20invalid%20or%20duplicate%20providers.%20Remove%20and%20re-add%20them%20if%20needed%2C%20and%20make%20sure%20provider%20names%20match%20the%20expected%20format%20%28e.g.%2C%20%60azure_openai%60%20or%20%60langgenius/azure_openai%60%2C%20not%20with%20two%20slashes%29%20%5B%5Bsource%5D%5D%28https%3A//github.com/langgenius/dify/issues/25775%29.%0A-%20Review%20your%20plugin%20configurations.%20Outdated%20plugins%20or%20missing%20expected%20keys%20in%20plugin/tool%20responses%20can%20cause%20500%20errors%20in%20agent%20workflows.%20Try%20upgrading%20plugins%20and%20ensure%20your%20workflow%20logic%20handles%20missing%20keys%20defensively%20%5B%5Bsource%5D%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1706%29.%0A-%20Test%20with%20a%20simple%20agent%20or%20workflow%20to%20see%20if%20the%20error%20persists.%20If%20it%20does%2C%20it%20may%20indicate%20a%20system-wide%20backend%20issue.%0A%0ASince%20you%E2%80%99re%20on%20the%20cloud%20version%20and%20don%E2%80%99t%20have%20access%20to%20backend%20logs%2C%20if%20the%20problem%20affects%20all%20agents%20and%20workflows%20and%20persists%20after%20checking%20the%20above%2C%20it%E2%80%99s%20likely%20a%20backend%20or%20infrastructure%20issue%20on%20the%20Dify%20Cloud%20side.%20In%20this%20case%2C%20gather%20as%20much%20detail%20as%20possible%20%28steps%20to%20reproduce%2C%20error%20messages%2C%20affected%20agents/workflows%2C%20and%20any%20recent%20changes%29%20and%20escalate%20to%20Dify%20Cloud%20support%20for%20further%20investigation%20%5B%5Bsource%5D%5D%28https%3A//github.com/langgenius/dify/issues/20306%29.%0A%0AIf%20you%20notice%20any%20recent%20changes%20in%20your%20workspace%20%28like%20new%20model%20providers%2C%20plugin%20updates%2C%20or%20workflow%20edits%29%2C%20try%20reverting%20those%20to%20see%20if%20the%20issue%20resolves.%20If%20you%20see%20a%20pattern%20%28e.g.%2C%20only%20certain%20plugins%20or%20models%20trigger%20the%20error%29%2C%20that%20info%20will%20help%20narrow%20down%20the%20root%20cause.)&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/29693)
yindo commented 2026-02-21 20:10:31 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 15, 2025):

What's your model provider?

@crazywoola commented on GitHub (Dec 15, 2025): What's your model provider?
yindo commented 2026-02-21 20:10:31 -05:00
Author
Owner
Copy Link
Copy Source

@Kronkmeister commented on GitHub (Dec 16, 2025):

Image

OpenAI mainly, and cohere (RAG).

Also by now I have replaced the APIs with no success. And also downgraded to 0.2.6 (and upgraded to 0.2.8) with no success and the same issue remains.

At first I thought it might be because of the Knowledgebase not working but the agents that don't use a knowledgebase also don't work.

There were no changes to the agents made over the last weeks prior to this error. It just stopped working.

@Kronkmeister commented on GitHub (Dec 16, 2025): <img width="744" height="350" alt="Image" src="https://github.com/user-attachments/assets/5e05880a-4965-445f-982e-4ff458716571" /> OpenAI mainly, and cohere (RAG). Also by now I have replaced the APIs with no success. And also downgraded to 0.2.6 (and upgraded to 0.2.8) with no success and the same issue remains. At first I thought it might be because of the Knowledgebase not working but the agents that don't use a knowledgebase also don't work. There were no changes to the agents made over the last weeks prior to this error. It just stopped working.
yindo commented 2026-02-21 20:10:31 -05:00
Author
Owner
Copy Link
Copy Source

@Kronkmeister commented on GitHub (Dec 17, 2025):

Okay, found the issue. It is a simple rate limit.

Image
@Kronkmeister commented on GitHub (Dec 17, 2025): Okay, found the issue. It is a simple rate limit. <img width="1102" height="706" alt="Image" src="https://github.com/user-attachments/assets/c89ee9cc-5f32-4cd8-bb88-b4c6b7733d8f" />
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#21061
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?