Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initiating any interface request with Javascript in the "Code Execution" node will result in an error: "errno: -3001, code: 'EAI_AGAIN', syscall: 'getaddrinfo', hostname: 'www.baidu.com'" #11842

Closed
5 tasks done
weiweimaodetuzi opened this issue Dec 19, 2024 · 1 comment
Labels
🐞 bug Something isn't working 🤔 cant-reproduce We can not reproduce it or the information is limited

Comments

@weiweimaodetuzi
Copy link

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

0.6.10

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

image
image

✔️ Expected Behavior

"Code Execution" node can initiating interface request

❌ Actual Behavior

Error: 'EAI_AGAIN'

@dosubot dosubot bot added 🐞 bug Something isn't working 🤔 cant-reproduce We can not reproduce it or the information is limited labels Dec 19, 2024
Copy link

dosubot bot commented Dec 19, 2024

@weiweimaodetuzi Hello there! I'm here to help you with any bugs, questions, or contributions. Let's work together to solve this issue.

The error EAI_AGAIN typically indicates a DNS resolution issue, meaning the system is having trouble resolving the hostname to an IP address. In Dify's self-hosted environment, the 'Code Execution' node is sandboxed for security reasons, which restricts network requests, including DNS lookups [1][2][3].

To address this issue, you might consider the following steps:

  1. Check DNS Configuration: Ensure that the DNS settings on your self-hosted environment are correctly configured. This might involve checking your Docker or server network settings to ensure they can resolve external hostnames.

  2. Network Access: Verify that the sandbox environment has the necessary permissions to access external networks. This might require adjusting firewall settings or network policies.

  3. Local DNS Server: If possible, configure a local DNS server that the sandbox can access, which might help in resolving external hostnames more reliably.

  4. Alternative Testing: As a workaround, test the network request outside of the sandboxed environment to ensure that the issue is specific to the sandbox restrictions.

These steps should help in diagnosing and potentially resolving the DNS resolution issue you're encountering.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working 🤔 cant-reproduce We can not reproduce it or the information is limited
Projects
None yet
Development

No branches or pull requests

2 participants