Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugins install fail #14574

Open
5 tasks done
meitianjinbu opened this issue Feb 28, 2025 · 2 comments
Open
5 tasks done

Plugins install fail #14574

meitianjinbu opened this issue Feb 28, 2025 · 2 comments
Labels
🐞 bug Something isn't working

Comments

@meitianjinbu
Copy link

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.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

install online or offline, always failed.
error information: init environment for plugin langgenius/xinference:0.0.2 failed too many times, you should consider the package is corrupted or your network is unstable

✔️ Expected Behavior

install well

❌ Actual Behavior

install fail

@dosubot dosubot bot added the 🐞 bug Something isn't working label Feb 28, 2025
Copy link

dosubot bot commented Feb 28, 2025

Hey @meitianjinbu! 👋 I'm here to help you with any bugs, questions, or contributions while you wait for a human maintainer. Let's tackle this issue together!

I found some relevant information that might help with your issue regarding plugin installation failures in Dify.

  1. Similar Threads: There is a similar open issue titled "Plugin install too slow" that might be related to your problem [1]. Additionally, a closed issue suggested that if you are using Docker on Windows, you can try placing the entire dify/docker directory on the WSL filesystem or add PLUGIN_WORKING_PATH=/app/cwd to your .env file to address performance issues related to file access on NTFS volumes [2].

  2. Error Messages: The error message you encountered suggests that the plugin might be corrupted or there is network instability. Specific logs or error messages during plugin installation failures can provide more insight. For instance, slow SQL queries and record not found errors are common indicators [3].

  3. Troubleshooting Steps: You can try adding FORCE_VERIFYING_SIGNATURE=false to your .env configuration file. This allows the installation of plugins not verified in the Dify Marketplace, but it's recommended to test these plugins in a sandbox environment first [4].

These steps and insights might help you resolve the plugin installation issue. If the problem persists, reviewing the backend logs for specific error messages could provide further clues.

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

@kevintsai1202
Copy link

Did you install Docker Desktop on Windows? Try adding PLUGIN_WORKING_PATH=/app/cwd at the end of /dify/docker/.env, then restart Docker Compose and see if it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants