plugin cannot be found in the plugin library #169

Open
opened 2026-02-16 00:20:18 -05:00 by yindo · 3 comments
Owner

Originally created by @Human-Torch-cpu on GitHub (Aug 5, 2025).

Self Checks

To make sure we get to you in time, please check the following :)

  • 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."

Versions

  1. dify-plugin-daemon Version 1.7.1
  2. dify-api Version 1.7.1

Describe the bug
The ollama-plugin cannot be found in the plugin library
I Can't find other plugins, too

To Reproduce
Steps to reproduce the behavior:
1.I took the download warehouse compressed package because git clone takes too long.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
Image

Image

Additional context
Add any other context about the problem here.

Originally created by @Human-Torch-cpu on GitHub (Aug 5, 2025). **Self Checks** To make sure we get to you in time, please check the following :) - [ ] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify-plugin-daemon/issues), including closed ones. - [ ] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [ ] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [ ] "Please do not modify this template :) and fill in all the required fields." **Versions** 1. dify-plugin-daemon Version 1.7.1 2. dify-api Version 1.7.1 **Describe the bug** The ollama-plugin cannot be found in the plugin library **I Can't find other plugins, too** **To Reproduce** Steps to reproduce the behavior: 1.I took the download warehouse compressed package because git clone takes too long. **Expected behavior** A clear and concise description of what you expected to happen. **Screenshots** <img width="919" height="86" alt="Image" src="https://github.com/user-attachments/assets/5f53dbce-f358-4115-8082-dcfd2b6bad66" /> <img width="912" height="89" alt="Image" src="https://github.com/user-attachments/assets/15c2d77b-7bbf-458a-b649-4735b2d03151" /> **Additional context** Add any other context about the problem here.
Author
Owner

@wodeshijie33941 commented on GitHub (Aug 6, 2025):

If you are installing the plugin manually, in addition to downloading the plugin, you also need to insert the plugin information into the database table - "plugins".

Because running a workflow or agent requires first retrieving plugin information from the database, and then notifying the "dify_plugin_daemon" to load the plugin and run the plugin logic.

If the relevant plugin information cannot be found in the database table - "plugins", it is impossible to know which node the plugin is installed on, resulting in the workflow being unable to continue running and then reporting an error as you can see.

It is recommended to install plugins directly through the DIY marketplace, as this will avoid many unnecessary troubles.

@wodeshijie33941 commented on GitHub (Aug 6, 2025): If you are installing the plugin manually, in addition to downloading the plugin, you also need to insert the plugin information into the database table - "plugins". Because running a workflow or agent requires first retrieving plugin information from the database, and then notifying the "dify_plugin_daemon" to load the plugin and run the plugin logic. If the relevant plugin information cannot be found in the database table - "plugins", it is impossible to know which node the plugin is installed on, resulting in the workflow being unable to continue running and then reporting an error as you can see. It is recommended to install plugins directly through the DIY marketplace, as this will avoid many unnecessary troubles.
Author
Owner

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

First, enter the plugin docker image and check if the plugin you installed is in the cwd directory. Second, connect to the dify-plugin database and check the relevant tables to see if there is any installation information for your plugin. If there is no relevant data in the database, delete the plugin from the cwd directory and force a reinstallation.

@xiaomeixw commented on GitHub (Aug 12, 2025): First, enter the plugin docker image and check if the plugin you installed is in the cwd directory. Second, connect to the dify-plugin database and check the relevant tables to see if there is any installation information for your plugin. If there is no relevant data in the database, delete the plugin from the cwd directory and force a reinstallation.
Author
Owner

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

There is no need to deliberately install from the Dify plugin marketplace. Local installation or GitHub installation is also possible. Even using an offline package for installation is acceptable. As long as the upload + install steps are followed, it will work.

@xiaomeixw commented on GitHub (Aug 12, 2025): There is no need to deliberately install from the Dify plugin marketplace. Local installation or GitHub installation is also possible. Even using an offline package for installation is acceptable. As long as the upload + install steps are followed, it will work.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugin-daemon#169