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

[Errno 111] Connection refused #21043

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

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

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Image

request node http://192.168.56.66:5023/api/get_customer_data/C00001 return [Errno 111] Connection refused:

2025-12-15 03:36:44.771 WARNING [Thread-1519 (_generate_worker)] [ssrf_proxy.py:79] - Request to URL http://192.168.56.66:5023/api/get_customer_data/C00001 failed on attempt 1: [Errno 111] Connection refused
2025-12-15 03:36:44.771 WARNING [Thread-1519 (_generate_worker)] [node.py:109] - http request node 1764059339750 failed to run: [Errno 111] Connection refused

.evn config
HTTP_PROXY=http://10.159.86.251:8080/
HTTPS_PROXY=https://10.159.86.251:8080/
NO_PROXY=127.0.0.1,localhost,192.168.56.66,192.168.56.11,fubontesting.local,dify-nginx,open-webui,plugin_daemon,vllm.uat1.fubonhk.local

plugin_daeman cofig
HTTPS_PROXY: http://10.159.86.251:8080/
NO_PROXY: ${NO_PROXY:-}

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @liaoduanyong on GitHub (Dec 14, 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] 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] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. <img width="1170" height="376" alt="Image" src="https://github.com/user-attachments/assets/e354f25a-a77e-48a2-b00f-441623c4ffa3" /> request node http://192.168.56.66:5023/api/get_customer_data/C00001 return [Errno 111] Connection refused: 2025-12-15 03:36:44.771 WARNING [Thread-1519 (_generate_worker)] [ssrf_proxy.py:79] - Request to URL http://192.168.56.66:5023/api/get_customer_data/C00001 failed on attempt 1: [Errno 111] Connection refused 2025-12-15 03:36:44.771 WARNING [Thread-1519 (_generate_worker)] [node.py:109] - http request node 1764059339750 failed to run: [Errno 111] Connection refused .evn config HTTP_PROXY=http://10.159.86.251:8080/ HTTPS_PROXY=https://10.159.86.251:8080/ NO_PROXY=127.0.0.1,localhost,192.168.56.66,192.168.56.11,fubontesting.local,dify-nginx,open-webui,plugin_daemon,vllm.uat1.fubonhk.local plugin_daeman cofig HTTPS_PROXY: http://10.159.86.251:8080/ NO_PROXY: ${NO_PROXY:-} ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 🐞 bug label 2026-02-21 20:10:25 -05:00
yindo closed this issue 2026-02-21 20:10:25 -05:00
yindo commented 2026-02-21 20:10:25 -05:00
Author
Owner
Copy Link
Copy Source

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

The error is likely caused by one of these common issues in Dockerized Dify setups:

  • The API server at 192.168.56.66:5023 is not running, not listening, or not reachable from the Dify container. Try running curl or telnet to that IP and port from inside the Dify container to confirm connectivity.
  • If the API server is running on your host, make sure the port is exposed and mapped in your docker-compose.yaml. In Docker, 127.0.0.1/localhost inside a container does not refer to the host—use the host's LAN IP (like 192.168.56.66) and ensure the port is open and mapped "source", "source".
  • The Dify workflow HTTP request node uses its own SSRF proxy config (SSRF_PROXY_ALL_URL, SSRF_PROXY_HTTP_URL, SSRF_PROXY_HTTPS_URL) and does not automatically inherit HTTP_PROXY/NO_PROXY from the environment. If you want direct access to local IPs, make sure these SSRF proxy variables are unset or set to allow direct connections "source".
  • NO_PROXY should include all relevant IPs, hostnames, and service names, and you should set both uppercase and lowercase variants (NO_PROXY, no_proxy) in your environment, as some libraries only recognize one or the other "source".
  • If you suspect proxy interference, try unsetting HTTP_PROXY and HTTPS_PROXY inside the container and see if the error changes.

If you check these areas and still see the error, share the results of a curl or telnet test from inside the Dify container to 192.168.56.66:5023, and confirm your SSRF proxy and docker-compose port mappings.

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 --> The error is likely caused by one of these common issues in Dockerized Dify setups: - The API server at 192.168.56.66:5023 is not running, not listening, or not reachable from the Dify container. Try running curl or telnet to that IP and port from inside the Dify container to confirm connectivity. - If the API server is running on your host, make sure the port is exposed and mapped in your docker-compose.yaml. In Docker, 127.0.0.1/localhost inside a container does not refer to the host—use the host's LAN IP (like 192.168.56.66) and ensure the port is open and mapped ["source"](https://github.com/langgenius/dify-official-plugins/issues/1127), ["source"](https://github.com/langgenius/dify-official-plugins/issues/1816). - The Dify workflow HTTP request node uses its own SSRF proxy config (SSRF_PROXY_ALL_URL, SSRF_PROXY_HTTP_URL, SSRF_PROXY_HTTPS_URL) and does not automatically inherit HTTP_PROXY/NO_PROXY from the environment. If you want direct access to local IPs, make sure these SSRF proxy variables are unset or set to allow direct connections ["source"](https://github.com/langgenius/dify/blob/094f417b32aea22a57b34b1165d93cae4ed82a3b/api/core/helper/ssrf_proxy.py#L0-L139). - NO_PROXY should include all relevant IPs, hostnames, and service names, and you should set both uppercase and lowercase variants (NO_PROXY, no_proxy) in your environment, as some libraries only recognize one or the other ["source"](https://github.com/langgenius/dify-official-plugins/issues/1089). - If you suspect proxy interference, try unsetting HTTP_PROXY and HTTPS_PROXY inside the container and see if the error changes. If you check these areas and still see the error, share the results of a curl or telnet test from inside the Dify container to 192.168.56.66:5023, and confirm your SSRF proxy and docker-compose port mappings. <!-- 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/b75b93f5-7382-4b98-a753-590390234660?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/b75b93f5-7382-4b98-a753-590390234660?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/b75b93f5-7382-4b98-a753-590390234660?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/b75b93f5-7382-4b98-a753-590390234660?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b75b93f5-7382-4b98-a753-590390234660?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/b75b93f5-7382-4b98-a753-590390234660?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b75b93f5-7382-4b98-a753-590390234660?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%20error%20is%20likely%20caused%20by%20one%20of%20these%20common%20issues%20in%20Dockerized%20Dify%20setups%3A%0A%0A-%20The%20API%20server%20at%20192.168.56.66%3A5023%20is%20not%20running%2C%20not%20listening%2C%20or%20not%20reachable%20from%20the%20Dify%20container.%20Try%20running%20curl%20or%20telnet%20to%20that%20IP%20and%20port%20from%20inside%20the%20Dify%20container%20to%20confirm%20connectivity.%0A-%20If%20the%20API%20server%20is%20running%20on%20your%20host%2C%20make%20sure%20the%20port%20is%20exposed%20and%20mapped%20in%20your%20docker-compose.yaml.%20In%20Docker%2C%20127.0.0.1/localhost%20inside%20a%20container%20does%20not%20refer%20to%20the%20host%E2%80%94use%20the%20host%27s%20LAN%20IP%20%28like%20192.168.56.66%29%20and%20ensure%20the%20port%20is%20open%20and%20mapped%20%5B%22source%22%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1127%29%2C%20%5B%22source%22%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1816%29.%0A-%20The%20Dify%20workflow%20HTTP%20request%20node%20uses%20its%20own%20SSRF%20proxy%20config%20%28SSRF_PROXY_ALL_URL%2C%20SSRF_PROXY_HTTP_URL%2C%20SSRF_PROXY_HTTPS_URL%29%20and%20does%20not%20automatically%20inherit%20HTTP_PROXY/NO_PROXY%20from%20the%20environment.%20If%20you%20want%20direct%20access%20to%20local%20IPs%2C%20make%20sure%20these%20SSRF%20proxy%20variables%20are%20unset%20or%20set%20to%20allow%20direct%20connections%20%5B%22source%22%5D%28https%3A//github.com/langgenius/dify/blob/094f417b32aea22a57b34b1165d93cae4ed82a3b/api/core/helper/ssrf_proxy.py%23L0-L139%29.%0A-%20NO_PROXY%20should%20include%20all%20relevant%20IPs%2C%20hostnames%2C%20and%20service%20names%2C%20and%20you%20should%20set%20both%20uppercase%20and%20lowercase%20variants%20%28NO_PROXY%2C%20no_proxy%29%20in%20your%20environment%2C%20as%20some%20libraries%20only%20recognize%20one%20or%20the%20other%20%5B%22source%22%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1089%29.%0A-%20If%20you%20suspect%20proxy%20interference%2C%20try%20unsetting%20HTTP_PROXY%20and%20HTTPS_PROXY%20inside%20the%20container%20and%20see%20if%20the%20error%20changes.%0A%0AIf%20you%20check%20these%20areas%20and%20still%20see%20the%20error%2C%20share%20the%20results%20of%20a%20curl%20or%20telnet%20test%20from%20inside%20the%20Dify%20container%20to%20192.168.56.66%3A5023%2C%20and%20confirm%20your%20SSRF%20proxy%20and%20docker-compose%20port%20mappings.)&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/29656)
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#21043
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?