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

503 and 500 Errors When Sending Concurrent Requests on Dify Sandbox #16318

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

Originally created by @swathyhealer on GitHub (Aug 21, 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.5.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

send 20 concurrent requests dify application

✔️ Expected Behavior

should return the workflow result

❌ Actual Behavior

When sending concurrent requests to the Dify sandbox environment, we frequently receive 503 Service Unavailable and 500 Internal Server Error responses.

Sample response (503):
{"message":"Request failed with status code 503"}

Originally created by @swathyhealer on GitHub (Aug 21, 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.5.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce send 20 concurrent requests dify application ### ✔️ Expected Behavior should return the workflow result ### ❌ Actual Behavior When sending concurrent requests to the Dify sandbox environment, we frequently receive 503 Service Unavailable and 500 Internal Server Error responses. Sample response (503): {"message":"Request failed with status code 503"}
yindo added the 🐞 bugoutdatedwont-fix labels 2026-02-21 19:25:37 -05:00
yindo closed this issue 2026-02-21 19:25:38 -05:00
yindo commented 2026-02-21 19:25:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 21, 2025):

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

Frequent 503 and 500 errors under concurrent requests in self-hosted Dify (Docker) are often linked to resource exhaustion, proxy configuration, or network issues. For 503 errors, check if your requests are hitting internal services—by default, Dify routes HTTP requests through a Squid proxy that blocks internal addresses. Update the ACLs in docker/ssrf_proxy/squid.conf.template to allow your internal network or domains, then rebuild/restart the proxy container. If you use self-signed SSL certs, you can toggle SSL verification in the HTTP Request node for debugging, but only do this in development environments. Also, adding extra_hosts in your Docker Compose config can help with internal domain resolution. Enable "Error on failure" in the HTTP Request node for more detailed error info. Review your Docker resource limits (CPU, memory, worker concurrency) and ensure all dependent services are running and reachable. For persistent network-related 503s, verify your HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables, and check firewall rules between containers. For 500 errors, check backend logs for signs of connection pool exhaustion or unhandled exceptions—recent Dify versions improved concurrency by using Celery for async workflow execution and explicit DB session management, so upgrading may help if you’re on an older release. More details and config tips are available in these threads:
Proxy config and internal network access
General 503 troubleshooting
Sandbox container config issues

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Aug 21, 2025): <!-- Greeting --> Hi @swathyhealer! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> Frequent 503 and 500 errors under concurrent requests in self-hosted Dify (Docker) are often linked to resource exhaustion, proxy configuration, or network issues. For 503 errors, check if your requests are hitting internal services—by default, Dify routes HTTP requests through a Squid proxy that blocks internal addresses. Update the ACLs in `docker/ssrf_proxy/squid.conf.template` to allow your internal network or domains, then rebuild/restart the proxy container. If you use self-signed SSL certs, you can toggle SSL verification in the HTTP Request node for debugging, but only do this in development environments. Also, adding `extra_hosts` in your Docker Compose config can help with internal domain resolution. Enable "Error on failure" in the HTTP Request node for more detailed error info. Review your Docker resource limits (CPU, memory, worker concurrency) and ensure all dependent services are running and reachable. For persistent network-related 503s, verify your `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables, and check firewall rules between containers. For 500 errors, check backend logs for signs of connection pool exhaustion or unhandled exceptions—recent Dify versions improved concurrency by using Celery for async workflow execution and explicit DB session management, so upgrading may help if you’re on an older release. More details and config tips are available in these threads: [Proxy config and internal network access](https://github.com/langgenius/dify/issues/22612#issuecomment-3086577978) [General 503 troubleshooting](https://github.com/langgenius/dify/issues/14948#issuecomment-2699638806) [Sandbox container config issues](https://github.com/langgenius/dify/issues/23686) <!-- 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/9eba3374-7d59-48a0-9d60-e97f309cd63a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9eba3374-7d59-48a0-9d60-e97f309cd63a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9eba3374-7d59-48a0-9d60-e97f309cd63a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9eba3374-7d59-48a0-9d60-e97f309cd63a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9eba3374-7d59-48a0-9d60-e97f309cd63a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9eba3374-7d59-48a0-9d60-e97f309cd63a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9eba3374-7d59-48a0-9d60-e97f309cd63a?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&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/24272)
yindo commented 2026-02-21 19:25:38 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 21, 2025):

The version is almost 2 yrs ago. :)

@crazywoola commented on GitHub (Aug 21, 2025): The version is almost 2 yrs ago. :)
yindo commented 2026-02-21 19:25:38 -05:00
Author
Owner
Copy Link
Copy Source

@swathyhealer commented on GitHub (Aug 21, 2025):

@crazywoola
sorry , my bad.
the version is 1.5.1.
could you please remove the "outdated" tag and reopen the issue

@swathyhealer commented on GitHub (Aug 21, 2025): @crazywoola sorry , my bad. the version is 1.5.1. could you please remove the "outdated" tag and reopen the issue
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 outdated wont-fix 🐞 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#16318
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?