LLM节点报错Request to Plugin Daemon Service failed-500n

[libin1219]

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.

Content

LLM node error: Request to Plugin Daemon Service failed-500 Do I need to modify any configuration in .env?

[dosubot[bot]]

The "Request to Plugin Daemon Service failed-500" error usually means the LLM node can't communicate properly with the plugin daemon service due to a server-side issue. This is often caused by misconfiguration, network problems (especially with Docker), timeouts, or plugin dependency failures.

Check these .env variables and settings:

• PLUGIN_DAEMON_URL: Make sure this points to the correct address where your plugin daemon is running (default is http://127.0.0.1:5002). If you're using Docker, avoid localhost/127.0.0.1—use host.docker.internal or your host's LAN IP instead if needed.
• PLUGIN_DAEMON_KEY: Should match the key expected by the plugin daemon for authentication.
• SANDBOX_ENABLE_NETWORK=true: Set this if your plugins need network access.
• If you see timeouts or dependency install failures, try increasing PYTHON_ENV_INIT_TIMEOUT and UV_HTTP_TIMEOUT in your plugin_daemon environment. You can also set a PyPI mirror (PIP_MIRROR_URL) for faster dependency downloads, especially if you're in a region with slow access to pypi.org.
• After changing .env or docker-compose settings, restart the relevant containers.

Also, check that the plugin daemon service is running and accessible, and review its logs for more details. If you recently updated Dify, make sure your plugin daemon image is up to date (the latest is 0.5.2-local as of late December 2025) source.

More troubleshooting tips and .env variable details can be found in these references:

• Plugin daemon .env example
• Common causes and fixes for 500 errors
• Timeouts and dependency install issues

If the error persists after checking these, review your Docker and plugin daemon logs for more clues.

To reply, just mention @dosu.

---

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

   

[libin1219]

The execution time is fine when it's three minutes, could it be related to the network?

[libin1219]

Or it may be related to the size of the uploaded video.

[libin1219]

Four minutes later, an error message will appear: Request to Plugin Daemon Service failed-500.

[gubinjie]

@libin1219 Is there a solution to this? When I upload a file for gemini to parse, it will appear when the file is too large