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

Under the premise that the model provider plugin has been created and the API uploaded, using the LLM node cannot find the corresponding node #16016

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

Originally created by @2510466299 on GitHub (Aug 9, 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.7.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Under the premise that the model provider plugin has been created and the API uploaded, using the LLM node cannot find the corresponding node

Image Image Image

✔️ Expected Behavior

I hope the node can run normally

❌ Actual Behavior

Actually, it will report an error, PluginDaemonInternalServerError: no available node, plugin not found, or internal server error

Originally created by @2510466299 on GitHub (Aug 9, 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.7.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Under the premise that the model provider plugin has been created and the API uploaded, using the LLM node cannot find the corresponding node <img width="1183" height="403" alt="Image" src="https://github.com/user-attachments/assets/8ce58d98-c656-49b4-842d-a3c1c87a1876" /> <img width="2560" height="690" alt="Image" src="https://github.com/user-attachments/assets/2a67b09c-d1c8-4077-a4fb-e7962e80dd81" /> <img width="756" height="324" alt="Image" src="https://github.com/user-attachments/assets/e06c0971-dbe3-42fe-ac8e-e1b30e865c8d" /> ### ✔️ Expected Behavior I hope the node can run normally ### ❌ Actual Behavior Actually, it will report an error, PluginDaemonInternalServerError: no available node, plugin not found, or internal server error
yindo added the 🐞 bug label 2026-02-21 19:24:21 -05:00
yindo closed this issue 2026-02-21 19:24:21 -05:00
yindo commented 2026-02-21 19:24:21 -05:00
Author
Owner
Copy Link
Copy Source

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

This error is common in self-hosted Docker setups and usually means the plugin daemon can't find or load your model provider plugin, even if it appears in the UI. The most frequent causes are: plugin dependency installation failures (often due to network timeouts), incomplete plugin registration, or misconfigured Docker environment variables. Here’s a focused troubleshooting checklist:

  1. Check plugin daemon health: Make sure the plugin_daemon service is running and accessible. If it’s not, plugins won’t be available to nodes [source].

  2. Dependency installation: Sometimes, plugin dependencies fail to install (especially in slow or restricted networks). Enter the plugin daemon container and run pip install -r requirements.txt in your plugin’s directory. Use a fast PyPI mirror if needed [source].

  3. Timeout settings: Increase PYTHON_ENV_INIT_TIMEOUT (e.g., 320 or higher) and PLUGIN_MAX_EXECUTION_TIMEOUT (e.g., 2400) in your docker-compose.yaml under the plugin_daemon service [source].

  4. Environment variables: Double-check that PLUGIN_DAEMON_URL, SANDBOX_ENABLE_NETWORK, PLUGIN_STORAGE_TYPE, and (if needed) PIP_MIRROR_URL are set correctly in your Docker environment [source].

  5. Database and directory cleanup: If the error persists, clear plugin-related tables in your database and delete plugin directories (like /app/storage/cwd/plugins/plugin, /plugin-working, /persistence, /plugin-root). Then restart the plugin daemon and reinstall plugins [source].

  6. Restart containers: After any changes, restart all relevant Docker containers, especially plugin_daemon [source].

  7. Avoid conflicts: Don’t run Dify from both source code and Docker at the same time, as this can cause plugin discovery failures [source].

  8. Check logs: Review both plugin daemon and backend logs for errors during plugin loading or registration. Look for dependency installation failures, timeouts, or missing/corrupted plugin metadata.

If your plugin metadata is incomplete (e.g., uniqueIdentifier is null), it can also cause this error and break plugin discovery in workflows [source].

Following these steps should help resolve the issue and make your custom model provider plugin available to the LLM node.

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 9, 2025): <!-- Answer --> This error is common in self-hosted Docker setups and usually means the plugin daemon can't find or load your model provider plugin, even if it appears in the UI. The most frequent causes are: plugin dependency installation failures (often due to network timeouts), incomplete plugin registration, or misconfigured Docker environment variables. Here’s a focused troubleshooting checklist: 1. **Check plugin daemon health**: Make sure the `plugin_daemon` service is running and accessible. If it’s not, plugins won’t be available to nodes [[source]](https://github.com/langgenius/dify/issues/21865). 2. **Dependency installation**: Sometimes, plugin dependencies fail to install (especially in slow or restricted networks). Enter the plugin daemon container and run `pip install -r requirements.txt` in your plugin’s directory. Use a fast PyPI mirror if needed [[source]](https://github.com/langgenius/dify/issues/14718). 3. **Timeout settings**: Increase `PYTHON_ENV_INIT_TIMEOUT` (e.g., 320 or higher) and `PLUGIN_MAX_EXECUTION_TIMEOUT` (e.g., 2400) in your `docker-compose.yaml` under the `plugin_daemon` service [[source]](https://github.com/langgenius/dify/issues/16999). 4. **Environment variables**: Double-check that `PLUGIN_DAEMON_URL`, `SANDBOX_ENABLE_NETWORK`, `PLUGIN_STORAGE_TYPE`, and (if needed) `PIP_MIRROR_URL` are set correctly in your Docker environment [[source]](https://github.com/langgenius/dify/issues/23236). 5. **Database and directory cleanup**: If the error persists, clear plugin-related tables in your database and delete plugin directories (like `/app/storage/cwd/plugins/plugin`, `/plugin-working`, `/persistence`, `/plugin-root`). Then restart the plugin daemon and reinstall plugins [[source]](https://github.com/langgenius/dify/issues/15940). 6. **Restart containers**: After any changes, restart all relevant Docker containers, especially `plugin_daemon` [[source]](https://github.com/langgenius/dify/issues/16999). 7. **Avoid conflicts**: Don’t run Dify from both source code and Docker at the same time, as this can cause plugin discovery failures [[source]](https://github.com/langgenius/dify/issues/18540). 8. **Check logs**: Review both plugin daemon and backend logs for errors during plugin loading or registration. Look for dependency installation failures, timeouts, or missing/corrupted plugin metadata. If your plugin metadata is incomplete (e.g., `uniqueIdentifier` is null), it can also cause this error and break plugin discovery in workflows [[source]](https://github.com/langgenius/dify/pull/23182). Following these steps should help resolve the issue and make your custom model provider plugin available to the LLM node. <!-- 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/76a4ef79-88b6-45d2-b7a7-5d044469da65?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/76a4ef79-88b6-45d2-b7a7-5d044469da65?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/76a4ef79-88b6-45d2-b7a7-5d044469da65?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/76a4ef79-88b6-45d2-b7a7-5d044469da65?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/76a4ef79-88b6-45d2-b7a7-5d044469da65?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/76a4ef79-88b6-45d2-b7a7-5d044469da65?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/76a4ef79-88b6-45d2-b7a7-5d044469da65?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/23665)
yindo commented 2026-02-21 19:24:21 -05:00
Author
Owner
Copy Link
Copy Source

@2510466299 commented on GitHub (Aug 12, 2025):

Thank you for your reply!

@2510466299 commented on GitHub (Aug 12, 2025): Thank you for your reply!
yindo commented 2026-02-21 19:24:21 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 12, 2025):

Hi, @2510466299. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that after creating and uploading a model provider plugin in Dify v1.7.1 (self-hosted via Docker), the LLM node cannot find the plugin, resulting in a "PluginDaemonInternalServerError."
  • I explained this is a common Docker setup issue caused by plugin daemon failing to load the plugin due to dependency installation failures, misconfigurations, or incomplete registration.
  • I provided a detailed troubleshooting checklist, including checking daemon health, dependencies, environment variables, and logs.
  • You acknowledged the response with thanks but have not provided further updates or confirmation if the issue was resolved.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify and if you need further assistance by commenting on this issue.
  • Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Sep 12, 2025): Hi, @2510466299. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that after creating and uploading a model provider plugin in Dify v1.7.1 (self-hosted via Docker), the LLM node cannot find the plugin, resulting in a "PluginDaemonInternalServerError." - I explained this is a common Docker setup issue caused by plugin daemon failing to load the plugin due to dependency installation failures, misconfigurations, or incomplete registration. - I provided a detailed troubleshooting checklist, including checking daemon health, dependencies, environment variables, and logs. - You acknowledged the response with thanks but have not provided further updates or confirmation if the issue was resolved. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify and if you need further assistance by commenting on this issue. - Otherwise, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
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#16016
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?