You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, @jun0315! I'm here to help you with any bugs, questions, or contributions related to Dify. Let's tackle this issue together while we wait for a human maintainer.
I found a similar open issue that might be relevant to your situation. The issue suggests that the problem could be related to how Dify differentiates between local and marketplace plugins. To address this, you should:
Ensure that the plugin is correctly identified as a local plugin by verifying the configuration settings, such as MARKETPLACE_ENABLED and MARKETPLACE_API_URL, in your environment to prevent unintended marketplace interactions.
Review the logic in your upgrade process to ensure that it correctly identifies and handles local plugins without attempting to fetch updates from the marketplace. This involves checking the conditions under which the HTTP request to the marketplace is triggered and ensuring they are not met for local plugins [1].
Additionally, for offline environments, you can consider using the "Local Upload" method by packaging your plugin into a .difypkg file and uploading it manually. This method is suitable for offline environments and allows you to maintain internal plugins without exposing sensitive information [2].
Self Checks
Dify version
1.0
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
related issue langgenius/dify-plugin-daemon#48
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
The text was updated successfully, but these errors were encountered: