Dify Webhook Returns 404 When Called, Deployed via Helm on Alibaba Cloud

[brt2056889806-alt]

Self Checks

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

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

Failed to execute code, which is likely a network issue, please check if the sandbox service is running. ( Error: [Errno -2] Name or service not known )

2. Additional context or comments

No response

[dosubot[bot]]

Hi @brt2056889806-alt! I'm Dosu and I’m helping the dify team.

The 404 error on your Dify webhook and the "[Errno -2] Name or service not known" error are most often caused by DNS or environment variable misconfigurations in Kubernetes Helm deployments.

First, make sure the webhook URL you’re calling matches the pattern /triggers/webhook/<webhook_id> and that the workflow containing the webhook node is published and active. If you recently changed the workflow, re-save or re-publish it to ensure the webhook is registered—otherwise, the backend will return a 404 until it syncs the new trigger. If the webhook ID is invalid or not found, Dify will return a 404 error as well reference.

For the "[Errno -2] Name or service not known" error, this usually means the worker pods (like dify-worker and dify-worker-beat) can’t resolve the sandbox service hostname. In Kubernetes, you should set the CODE_EXECUTION_ENDPOINT environment variable to the full DNS name, for example:
http://sandbox.<namespace>.svc.cluster.local:8194
Replace <namespace> with your actual namespace. Make sure this variable (and CODE_EXECUTION_API_KEY) is set in all relevant pods, not just dify-api reference.

Check that a Kubernetes Service named sandbox exists in the correct namespace and is healthy. You can test DNS resolution and connectivity from inside your pods using getent hosts sandbox.<namespace>.svc.cluster.local and by running a curl POST to the sandbox endpoint with the correct API key reference.

If you’re still seeing issues, review logs from dify-api, dify-worker, and dify-sandbox pods for DNS or network errors at the time of the webhook call, and check for any network policies or firewalls that might block inter-pod communication.

Let me know if you need help with specific configuration examples or troubleshooting steps.

To reply, just mention @dosu.

---

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