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

PluginDaemonInternalServerError: no available node, plugin not found #13143

New Issue
Closed
opened 2026-02-21 19:10:45 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:10:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @bb159 on GitHub (Apr 20, 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

Migrated dify from a laptop to a computer, only the volume folder was copied, and this issue occurred on startup.

✔️ Expected Behavior

Recall content from the knowledge base.

❌ Actual Behavior

ImagePluginDaemonInternalServerError: no available node, plugin not found，only able use this

Originally created by @bb159 on GitHub (Apr 20, 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 Migrated dify from a laptop to a computer, only the volume folder was copied, and this issue occurred on startup. ### ✔️ Expected Behavior Recall content from the knowledge base. ### ❌ Actual Behavior ![Image](https://github.com/user-attachments/assets/b84b998b-799c-4803-a8ee-d6bc121f282a)PluginDaemonInternalServerError: no available node, plugin not found，only able use this
yindo added the 🐞 bug label 2026-02-21 19:10:45 -05:00
yindo closed this issue 2026-02-21 19:10:45 -05:00
yindo commented 2026-02-21 19:10:45 -05:00
Author
Owner
Copy Link
Copy Source

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

Hello @bb159! I'm Dosu, your friendly bot here to help you tackle bugs, answer questions, and navigate contributions while we wait for a human maintainer. Let's get to the bottom of this together! 🚀

I found similar open issues that might help resolve the "PluginDaemonInternalServerError: no available node, plugin not found" error:

  1. Issue 17941 suggests increasing the Python environment initialization timeout by adding PYTHON_ENV_INIT_TIMEOUT: 320 to your docker-compose.yaml file and restarting your Dify instance. Additionally, clean up the database to remove conflicting plugin records and clear plugin directories. Ensure you are not running the application from both source code and Docker simultaneously [1].

  2. Issue 14654 recommends upgrading to Dify version 1.0.1 or later, modifying your docker-compose.yaml file to increase the plugin execution timeout, and adding specific environment variables to your .env file. If the error persists, clean the database or perform a complete database purge and fresh installation [2].

To resolve your issue, you can try the following steps:

  • Upgrade to Dify version 1.0.1 or later, if not already done.
  • Modify your docker-compose.yaml file to increase the plugin execution timeout: 
    plugin_daemon:
  environment:
    PLUGIN_MAX_EXECUTION_TIMEOUT: 2400
  • Add the following environment variables to your .env file: 
    PLUGIN_PYTHON_ENV_INIT_TIMEOUT=720
PIP_MIRROR_URL=https://mirrors.aliyun.com/pypi/simple
  • Ensure you're not running the application from both source code and Docker simultaneously.
  • Clean the database to remove conflicting provider records, or perform a complete database purge and fresh installation.
  • Restart your Docker containers: 
    docker compose down && docker compose up -d

These steps should help resolve the issue. If the problem persists, consider checking the specific SQL commands needed to clear plugin data from the dify_plugin database [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 20, 2025): <!-- Greeting --> Hello @bb159! I'm [Dosu](https://dosu.dev), your friendly bot here to help you tackle bugs, answer questions, and navigate contributions while we wait for a human maintainer. Let's get to the bottom of this together! 🚀 <!-- Answer --> I found similar open issues that might help resolve the "PluginDaemonInternalServerError: no available node, plugin not found" error: 1. **Issue [17941](https://github.com/langgenius/dify/issues/17941)** suggests increasing the Python environment initialization timeout by adding `PYTHON_ENV_INIT_TIMEOUT: 320` to your `docker-compose.yaml` file and restarting your Dify instance. Additionally, clean up the database to remove conflicting plugin records and clear plugin directories. Ensure you are not running the application from both source code and Docker simultaneously <sup>[[1]](https://github.com/langgenius/dify/issues/17941)</sup>. 2. **Issue [14654](https://github.com/langgenius/dify/issues/14654)** recommends upgrading to Dify version 1.0.1 or later, modifying your `docker-compose.yaml` file to increase the plugin execution timeout, and adding specific environment variables to your `.env` file. If the error persists, clean the database or perform a complete database purge and fresh installation <sup>[[2]](https://github.com/langgenius/dify/issues/14654)</sup>. To resolve your issue, you can try the following steps: - Upgrade to Dify version 1.0.1 or later, if not already done. - Modify your `docker-compose.yaml` file to increase the plugin execution timeout: ```yaml plugin_daemon: environment: PLUGIN_MAX_EXECUTION_TIMEOUT: 2400 ``` - Add the following environment variables to your `.env` file: ```sh PLUGIN_PYTHON_ENV_INIT_TIMEOUT=720 PIP_MIRROR_URL=https://mirrors.aliyun.com/pypi/simple ``` - Ensure you're not running the application from both source code and Docker simultaneously. - Clean the database to remove conflicting provider records, or perform a complete database purge and fresh installation. - Restart your Docker containers: ```bash docker compose down && docker compose up -d ``` These steps should help resolve the issue. If the problem persists, consider checking the specific SQL commands needed to clear plugin data from the `dify_plugin` database <sup>[[3]](https://github.com/langgenius/dify/issues/14718)</sup>. <!-- 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/7df6e9c5-4777-4887-b9d3-bc973cb44b7f?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/7df6e9c5-4777-4887-b9d3-bc973cb44b7f?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/7df6e9c5-4777-4887-b9d3-bc973cb44b7f?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/7df6e9c5-4777-4887-b9d3-bc973cb44b7f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7df6e9c5-4777-4887-b9d3-bc973cb44b7f?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/7df6e9c5-4777-4887-b9d3-bc973cb44b7f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/7df6e9c5-4777-4887-b9d3-bc973cb44b7f?feedback_type=other)</sup>
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#13143
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?