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

Run failed: [siliconflow] Error: PluginDaemonInternalServerError: no available node, plugin not found #12839

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

Originally created by @Vampxgg on GitHub (Apr 12, 2025).

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

1.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Run failed: [siliconflow] Error: PluginDaemonInternalServerError: no available node, plugin not found

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @Vampxgg on GitHub (Apr 12, 2025). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.1.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Run failed: [siliconflow] Error: PluginDaemonInternalServerError: no available node, plugin not found ![Image](https://github.com/user-attachments/assets/26a109f6-e6d6-4cdb-a1d7-e2cb09860645) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:09:19 -05:00
yindo closed this issue 2026-02-21 19:09:19 -05:00
yindo commented 2026-02-21 19:09:19 -05:00
Author
Owner
Copy Link
Copy Source

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

I found some similar open issues related to the "PluginDaemonInternalServerError: no available node, plugin not found" error in Dify:

  1. One suggested solution is to increase the Python environment initialization timeout by adding the following line to your docker-compose.yaml file:

    PYTHON_ENV_INIT_TIMEOUT: 320

    Restarting your Dify instance might also help resolve the issue [1].

  2. Another approach involves cleaning up the database to remove any conflicting plugin records and clearing plugin directories. You can execute specific SQL commands to clear plugin data from the dify_plugin database and remove plugin directories from:

    • /app/storage/cwd/plugins/plugin
    • /app/storage/cwd/plugins/plugin-working
    • /app/storage/cwd/plugins/persistence
    • /app/storage/cwd/plugins/plugin-root

    Afterward, restart the plugin daemon service and reinstall the plugins from the marketplace [2].

  3. Additionally, ensure that you are not running the application from both source code and Docker simultaneously, as this can cause data conflicts. If you are experiencing timeout issues, adjust the timeout settings in your docker-compose.yaml file and ensure the correct configuration in the docker-compose.middleware.yaml file [3].

These steps should help address the error you're encountering with the siliconflow plugin in Dify version 1.1.3.

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Apr 12, 2025): <!-- Answer --> I found some similar open issues related to the "PluginDaemonInternalServerError: no available node, plugin not found" error in Dify: 1. One suggested solution is to increase the Python environment initialization timeout by adding the following line to your `docker-compose.yaml` file: ```yaml PYTHON_ENV_INIT_TIMEOUT: 320 ``` Restarting your Dify instance might also help resolve the issue <sup>[[1]](https://github.com/langgenius/dify/issues/17472)</sup>. 2. Another approach involves cleaning up the database to remove any conflicting plugin records and clearing plugin directories. You can execute specific SQL commands to clear plugin data from the `dify_plugin` database and remove plugin directories from: - `/app/storage/cwd/plugins/plugin` - `/app/storage/cwd/plugins/plugin-working` - `/app/storage/cwd/plugins/persistence` - `/app/storage/cwd/plugins/plugin-root` Afterward, restart the plugin daemon service and reinstall the plugins from the marketplace <sup>[[2]](https://github.com/langgenius/dify/issues/15881)</sup>. 3. Additionally, ensure that you are not running the application from both source code and Docker simultaneously, as this can cause data conflicts. If you are experiencing timeout issues, adjust the timeout settings in your `docker-compose.yaml` file and ensure the correct configuration in the `docker-compose.middleware.yaml` file <sup>[[3]](https://github.com/langgenius/dify/issues/16553)</sup>. These steps should help address the error you're encountering with the siliconflow plugin in Dify version 1.1.3. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/b9bca5f3-f665-4d7f-9785-a2176a860c26?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/b9bca5f3-f665-4d7f-9785-a2176a860c26?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/b9bca5f3-f665-4d7f-9785-a2176a860c26?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/b9bca5f3-f665-4d7f-9785-a2176a860c26?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b9bca5f3-f665-4d7f-9785-a2176a860c26?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/b9bca5f3-f665-4d7f-9785-a2176a860c26?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b9bca5f3-f665-4d7f-9785-a2176a860c26?feedback_type=other)</sup>
yindo commented 2026-02-21 19:09:19 -05:00
Author
Owner
Copy Link
Copy Source

@ChasePassion commented on GitHub (May 16, 2025):

今天我也遇到这个问题，解决办法是把插件全部删除然后重新下载

@ChasePassion commented on GitHub (May 16, 2025): 今天我也遇到这个问题，解决办法是把插件全部删除然后重新下载
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#12839
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?