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

The readoperation timed outNo files were successfully processed #21036

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

Originally created by @xieshifeng985 on GitHub (Dec 14, 2025).

Originally assigned to: @fatelei on GitHub.

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.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When multiple users simultaneously upload files to the workflow intelligent agent for processing, an exception occurs as shown in the following figure. How can I solve this problem? Thank you

Image

✔️ Expected Behavior

My DIY workflow agent can support multiple users uploading files simultaneously without reporting any exceptions

❌ Actual Behavior

No response

Originally created by @xieshifeng985 on GitHub (Dec 14, 2025). Originally assigned to: @fatelei on GitHub. ### 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.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When multiple users simultaneously upload files to the workflow intelligent agent for processing, an exception occurs as shown in the following figure. How can I solve this problem? Thank you <img width="651" height="957" alt="Image" src="https://github.com/user-attachments/assets/00a28e2e-46d9-47a5-95c5-64f1ea7af26f" /> ### ✔️ Expected Behavior My DIY workflow agent can support multiple users uploading files simultaneously without reporting any exceptions ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 20:10:22 -05:00
yindo closed this issue 2026-02-21 20:10:22 -05:00
yindo commented 2026-02-21 20:10:22 -05:00
Author
Owner
Copy Link
Copy Source

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

Timeout errors like "read operation timed out" during concurrent file uploads in Dify self-hosted Docker setups are often caused by infrastructure or configuration limits, not just application code. To improve support for simultaneous uploads, increase these settings in your .env and docker-compose.yaml: HTTP_REQUEST_MAX_READ_TIMEOUT, HTTP_REQUEST_MAX_WRITE_TIMEOUT, GUNICORN_TIMEOUT, NGINX_PROXY_READ_TIMEOUT, NGINX_PROXY_SEND_TIMEOUT, WORKFLOW_MAX_EXECUTION_TIME, PLUGIN_DAEMON_TIMEOUT, and PLUGIN_MAX_EXECUTION_TIMEOUT. Also, raise worker counts and connection limits (SERVER_WORKER_AMOUNT, SERVER_WORKER_CONNECTIONS, GRAPH_ENGINE_MAX_WORKERS) to handle more parallel uploads. Make sure your Docker port mapping and file server URLs are correct (e.g., FILES_URL, INTERNAL_FILES_URL, port 5001) to avoid file access issues. After changing these, restart all containers and nginx for the new settings to take effect. If you still see timeouts, check backend logs for resource contention or misconfiguration. Recent Dify versions have improved file upload synchronization, so consider upgrading if concurrency is critical for your workflow.
Reference 1 | Reference 2 | Reference 3 | Reference 4

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 14, 2025): <!-- Answer --> Timeout errors like "read operation timed out" during concurrent file uploads in Dify self-hosted Docker setups are often caused by infrastructure or configuration limits, not just application code. To improve support for simultaneous uploads, increase these settings in your `.env` and `docker-compose.yaml`: `HTTP_REQUEST_MAX_READ_TIMEOUT`, `HTTP_REQUEST_MAX_WRITE_TIMEOUT`, `GUNICORN_TIMEOUT`, `NGINX_PROXY_READ_TIMEOUT`, `NGINX_PROXY_SEND_TIMEOUT`, `WORKFLOW_MAX_EXECUTION_TIME`, `PLUGIN_DAEMON_TIMEOUT`, and `PLUGIN_MAX_EXECUTION_TIMEOUT`. Also, raise worker counts and connection limits (`SERVER_WORKER_AMOUNT`, `SERVER_WORKER_CONNECTIONS`, `GRAPH_ENGINE_MAX_WORKERS`) to handle more parallel uploads. Make sure your Docker port mapping and file server URLs are correct (e.g., `FILES_URL`, `INTERNAL_FILES_URL`, port 5001) to avoid file access issues. After changing these, restart all containers and nginx for the new settings to take effect. If you still see timeouts, check backend logs for resource contention or misconfiguration. Recent Dify versions have improved file upload synchronization, so consider upgrading if concurrency is critical for your workflow. [Reference 1](https://github.com/langgenius/dify/issues/29025) | [Reference 2](https://github.com/langgenius/dify/issues/15203) | [Reference 3](https://github.com/langgenius/dify-docs/issues/471) | [Reference 4](https://github.com/langgenius/dify/pull/27981) <!-- 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/7870cfda-6555-4859-9565-67e0c5b49717?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/7870cfda-6555-4859-9565-67e0c5b49717?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/7870cfda-6555-4859-9565-67e0c5b49717?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/7870cfda-6555-4859-9565-67e0c5b49717?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7870cfda-6555-4859-9565-67e0c5b49717?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/7870cfda-6555-4859-9565-67e0c5b49717?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/7870cfda-6555-4859-9565-67e0c5b49717?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=Timeout%20errors%20like%20%22read%20operation%20timed%20out%22%20during%20concurrent%20file%20uploads%20in%20Dify%20self-hosted%20Docker%20setups%20are%20often%20caused%20by%20infrastructure%20or%20configuration%20limits%2C%20not%20just%20application%20code.%20To%20improve%20support%20for%20simultaneous%20uploads%2C%20increase%20these%20settings%20in%20your%20%60.env%60%20and%20%60docker-compose.yaml%60%3A%20%60HTTP_REQUEST_MAX_READ_TIMEOUT%60%2C%20%60HTTP_REQUEST_MAX_WRITE_TIMEOUT%60%2C%20%60GUNICORN_TIMEOUT%60%2C%20%60NGINX_PROXY_READ_TIMEOUT%60%2C%20%60NGINX_PROXY_SEND_TIMEOUT%60%2C%20%60WORKFLOW_MAX_EXECUTION_TIME%60%2C%20%60PLUGIN_DAEMON_TIMEOUT%60%2C%20and%20%60PLUGIN_MAX_EXECUTION_TIMEOUT%60.%20Also%2C%20raise%20worker%20counts%20and%20connection%20limits%20%28%60SERVER_WORKER_AMOUNT%60%2C%20%60SERVER_WORKER_CONNECTIONS%60%2C%20%60GRAPH_ENGINE_MAX_WORKERS%60%29%20to%20handle%20more%20parallel%20uploads.%20Make%20sure%20your%20Docker%20port%20mapping%20and%20file%20server%20URLs%20are%20correct%20%28e.g.%2C%20%60FILES_URL%60%2C%20%60INTERNAL_FILES_URL%60%2C%20port%205001%29%20to%20avoid%20file%20access%20issues.%20After%20changing%20these%2C%20restart%20all%20containers%20and%20nginx%20for%20the%20new%20settings%20to%20take%20effect.%20If%20you%20still%20see%20timeouts%2C%20check%20backend%20logs%20for%20resource%20contention%20or%20misconfiguration.%20Recent%20Dify%20versions%20have%20improved%20file%20upload%20synchronization%2C%20so%20consider%20upgrading%20if%20concurrency%20is%20critical%20for%20your%20workflow.%20%20%0A%5BReference%201%5D%28https%3A//github.com/langgenius/dify/issues/29025%29%20%7C%20%5BReference%202%5D%28https%3A//github.com/langgenius/dify/issues/15203%29%20%7C%20%5BReference%203%5D%28https%3A//github.com/langgenius/dify-docs/issues/471%29%20%7C%20%5BReference%204%5D%28https%3A//github.com/langgenius/dify/pull/27981%29)&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/29642)
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#21036
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?