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

Bug Report: Plugin was installed successfully, but i got plugin not found error while input API key #11999

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

Originally created by @hsiong on GitHub (Mar 23, 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.2

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

  1. install plugin in Plugin
  2. wait plugin install
  3. input API key

I've restarted plugin_daemon as mentioned in https://github.com/langgenius/dify/issues/16469, but it not worked

Image

Image

✔️ Expected Behavior

Able to enter API key in the model setup

❌ Actual Behavior

Image

Originally created by @hsiong on GitHub (Mar 23, 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.2 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce 1. install plugin in `Plugin` 2. wait plugin install 3. input API key I've restarted plugin_daemon as mentioned in https://github.com/langgenius/dify/issues/16469, but it not worked ![Image](https://github.com/user-attachments/assets/8797361b-3d8a-4490-aed2-44fde376c086) ![Image](https://github.com/user-attachments/assets/ab691321-c9aa-41c6-9378-21e7d5177562) ### ✔️ Expected Behavior Able to enter API key in the model setup ### ❌ Actual Behavior ![Image](https://github.com/user-attachments/assets/8e151a7b-b669-4956-8bf4-c8c4b68fc651)
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 19:05:12 -05:00
yindo closed this issue 2026-02-21 19:05:12 -05:00
yindo commented 2026-02-21 19:05:12 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 23, 2025):

There are similar threads addressing the "PluginDaemonInternalServerError: no available node, plugin not found" error in Dify version 1.1.2 on a self-hosted setup. Here are some steps that have been suggested to resolve this issue:

  1. Clear Plugin Data from the Database: Execute the following SQL commands in the dify_plugin database to clear plugin data:

    delete from plugin_installations where plugin_unique_identifier is not null;
delete from plugin_declarations where plugin_unique_identifier is not null;
delete from ai_model_installations where plugin_unique_identifier is not null;
delete from plugins where plugin_unique_identifier is not null;

  2. Clear Plugin Directories: Remove the contents of these directories:

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

  3. Restart the Plugin Daemon Service: After clearing the data, restart the plugin daemon service.

  4. Reinstall Plugins: Reinstall the plugins from the marketplace.

  5. Modify Docker Compose Configuration: Increase the plugin execution timeout by adding the following to your docker-compose.yaml:

    plugin_daemon:
  environment:
    PLUGIN_MAX_EXECUTION_TIMEOUT: 2400

  6. Increase Python Environment Initialization Timeout: Add this line to your docker-compose.yaml:

    PYTHON_ENV_INIT_TIMEOUT: 320

  7. Avoid Running from Both Source Code and Docker: Ensure you're not running the application from both source code and Docker simultaneously, as this can cause data conflicts.

  8. Remove Proxy Configurations: If using proxies, remove any proxy configurations from the plugin-daemon container in docker-compose.yaml.

  9. Try Earlier Plugin Versions: For specific plugins like Tongyi, using an earlier version (e.g., 0.04) might help if the latest version causes issues.

  10. Restart Docker Containers: After making these changes, restart your Docker containers:

    docker compose stop
docker compose up -d

These steps address plugin installation, database synchronization issues, and timeout settings that might be causing the error [1][2].

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 (Mar 23, 2025): <!-- Answer --> There are similar threads addressing the "PluginDaemonInternalServerError: no available node, plugin not found" error in Dify version 1.1.2 on a self-hosted setup. Here are some steps that have been suggested to resolve this issue: 1. **Clear Plugin Data from the Database**: Execute the following SQL commands in the `dify_plugin` database to clear plugin data: ```sql delete from plugin_installations where plugin_unique_identifier is not null; delete from plugin_declarations where plugin_unique_identifier is not null; delete from ai_model_installations where plugin_unique_identifier is not null; delete from plugins where plugin_unique_identifier is not null; ``` 2. **Clear Plugin Directories**: Remove the contents of these directories: - `/app/storage/cwd/plugins/plugin` - `/app/storage/cwd/plugins/plugin-working` - `/app/storage/cwd/plugins/persistence` - `/app/storage/cwd/plugins/plugin-root` 3. **Restart the Plugin Daemon Service**: After clearing the data, restart the plugin daemon service. 4. **Reinstall Plugins**: Reinstall the plugins from the marketplace. 5. **Modify Docker Compose Configuration**: Increase the plugin execution timeout by adding the following to your `docker-compose.yaml`: ```yaml plugin_daemon: environment: PLUGIN_MAX_EXECUTION_TIMEOUT: 2400 ``` 6. **Increase Python Environment Initialization Timeout**: Add this line to your `docker-compose.yaml`: ```yaml PYTHON_ENV_INIT_TIMEOUT: 320 ``` 7. **Avoid Running from Both Source Code and Docker**: Ensure you're not running the application from both source code and Docker simultaneously, as this can cause data conflicts. 8. **Remove Proxy Configurations**: If using proxies, remove any proxy configurations from the plugin-daemon container in `docker-compose.yaml`. 9. **Try Earlier Plugin Versions**: For specific plugins like Tongyi, using an earlier version (e.g., 0.04) might help if the latest version causes issues. 10. **Restart Docker Containers**: After making these changes, restart your Docker containers: ```bash docker compose stop docker compose up -d ``` These steps address plugin installation, database synchronization issues, and timeout settings that might be causing the error <sup>[[1]](https://github.com/langgenius/dify/issues/15530)</sup><sup>[[2]](https://github.com/langgenius/dify/issues/15940)</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/0d74cf25-caf7-4917-962a-7c700daeb104?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/0d74cf25-caf7-4917-962a-7c700daeb104?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/0d74cf25-caf7-4917-962a-7c700daeb104?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/0d74cf25-caf7-4917-962a-7c700daeb104?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0d74cf25-caf7-4917-962a-7c700daeb104?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/0d74cf25-caf7-4917-962a-7c700daeb104?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0d74cf25-caf7-4917-962a-7c700daeb104?feedback_type=other)</sup>
yindo commented 2026-02-21 19:05:12 -05:00
Author
Owner
Copy Link
Copy Source

@hsiong commented on GitHub (Mar 23, 2025):

You got me wrong. What i mean is: why does it still show plugin not found even after a successful installation

@dosu

@hsiong commented on GitHub (Mar 23, 2025): You got me wrong. What i mean is: why does it still show `plugin not found` even after a successful installation @dosu
yindo commented 2026-02-21 19:05:13 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 23, 2025):

The "plugin not found" error may still appear after a successful plugin installation due to Python dependencies not being installed within the default timeout period. To resolve this, you can increase the Python environment initialization timeout by adding the following line to your docker-compose.yaml:

PYTHON_ENV_INIT_TIMEOUT: 320

If the issue persists, you should clear plugin data from the database using specific SQL commands, clear plugin directories, restart the plugin daemon service, and reinstall the plugins. This process addresses the typical cause of the error, which is the failure of plugin installation due to timeout issues [1][2].

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 (Mar 23, 2025): <!-- Answer --> The "plugin not found" error may still appear after a successful plugin installation due to Python dependencies not being installed within the default timeout period. To resolve this, you can increase the Python environment initialization timeout by adding the following line to your `docker-compose.yaml`: ```yaml PYTHON_ENV_INIT_TIMEOUT: 320 ``` If the issue persists, you should clear plugin data from the database using specific SQL commands, clear plugin directories, restart the plugin daemon service, and reinstall the plugins. This process addresses the typical cause of the error, which is the failure of plugin installation due to timeout issues <sup>[[1]](https://github.com/langgenius/dify/issues/15454)</sup><sup>[[2]](https://github.com/langgenius/dify/issues/14562)</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/0d9338a4-15fb-44ee-ad48-e07c1b202b10?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/0d9338a4-15fb-44ee-ad48-e07c1b202b10?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/0d9338a4-15fb-44ee-ad48-e07c1b202b10?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/0d9338a4-15fb-44ee-ad48-e07c1b202b10?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0d9338a4-15fb-44ee-ad48-e07c1b202b10?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/0d9338a4-15fb-44ee-ad48-e07c1b202b10?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0d9338a4-15fb-44ee-ad48-e07c1b202b10?feedback_type=other)</sup>
yindo commented 2026-02-21 19:05:13 -05:00
Author
Owner
Copy Link
Copy Source

@hsiong commented on GitHub (Mar 23, 2025):

I've solved the problem by changing this file docker-compose.middleware.yaml; I don't know why setting it in the middleware.env didn't work

      PYTHON_ENV_INIT_TIMEOUT: ${PLUGIN_PYTHON_ENV_INIT_TIMEOUT:-60}
      PLUGIN_MAX_EXECUTION_TIMEOUT: ${PLUGIN_MAX_EXECUTION_TIMEOUT:-60}
      PIP_MIRROR_URL: ${PIP_MIRROR_URL:-https://pypi.tuna.tsinghua.edu.cn/simple}
@hsiong commented on GitHub (Mar 23, 2025): I've solved the problem by changing this file `docker-compose.middleware.yaml`; I don't know why setting it in the `middleware.env` didn't work ``` PYTHON_ENV_INIT_TIMEOUT: ${PLUGIN_PYTHON_ENV_INIT_TIMEOUT:-60} PLUGIN_MAX_EXECUTION_TIMEOUT: ${PLUGIN_MAX_EXECUTION_TIMEOUT:-60} PIP_MIRROR_URL: ${PIP_MIRROR_URL:-https://pypi.tuna.tsinghua.edu.cn/simple} ```
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 🤔 cant-reproduce
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#11999
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?