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

the PLUNIN content in .env #12992

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

Originally created by @fanfan-lucky on GitHub (Apr 16, 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.2.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I use "openAI API compatible" to add model, but always show "core.plugin.manager.exc.PluginDaemonInternalServerError: PluginDaemonInternalServerError: no available node, plugin not found", I doubt the environment variable in .env.example has some error, please see below default setting,
PLUGIN_STORAGE_TYPE=local
PLUGIN_STORAGE_LOCAL_ROOT=/app/storage
PLUGIN_WORKING_PATH=/app/storage/cwd
PLUGIN_INSTALLED_PATH=plugin
PLUGIN_PACKAGE_CACHE_PATH=plugin_packages
PLUGIN_MEDIA_CACHE_PATH=assets

so PLUGIN_WORKING_PATH is right? should it be /daemon_plugin/cwd?

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @fanfan-lucky on GitHub (Apr 16, 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.2.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I use "openAI API compatible" to add model, but always show "core.plugin.manager.exc.PluginDaemonInternalServerError: PluginDaemonInternalServerError: no available node, plugin not found", I doubt the environment variable in .env.example has some error, please see below default setting, PLUGIN_STORAGE_TYPE=local PLUGIN_STORAGE_LOCAL_ROOT=/app/storage PLUGIN_WORKING_PATH=/app/storage/cwd PLUGIN_INSTALLED_PATH=plugin PLUGIN_PACKAGE_CACHE_PATH=plugin_packages PLUGIN_MEDIA_CACHE_PATH=assets so PLUGIN_WORKING_PATH is right? should it be /daemon_plugin/cwd? ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🙏 help wanted label 2026-02-21 19:10:03 -05:00
yindo closed this issue 2026-02-21 19:10:03 -05:00
yindo commented 2026-02-21 19:10:04 -05:00
Author
Owner
Copy Link
Copy Source

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

The PLUGIN_WORKING_PATH in the .env file should be set to /app/storage/cwd, as indicated in the configuration example. This is the correct setting for the plugin daemon configuration in Dify [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 (Apr 16, 2025): <!-- Answer --> The `PLUGIN_WORKING_PATH` in the `.env` file should be set to `/app/storage/cwd`, as indicated in the configuration example. This is the correct setting for the plugin daemon configuration in Dify <sup>[[1]](https://github.com/langgenius/dify/issues/12635)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/main/docker/middleware.env.example)</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/85aacbd1-4350-46e4-bd4a-25b9de7d08ad?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/85aacbd1-4350-46e4-bd4a-25b9de7d08ad?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/85aacbd1-4350-46e4-bd4a-25b9de7d08ad?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/85aacbd1-4350-46e4-bd4a-25b9de7d08ad?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/85aacbd1-4350-46e4-bd4a-25b9de7d08ad?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/85aacbd1-4350-46e4-bd4a-25b9de7d08ad?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/85aacbd1-4350-46e4-bd4a-25b9de7d08ad?feedback_type=other)</sup>
yindo commented 2026-02-21 19:10:04 -05:00
Author
Owner
Copy Link
Copy Source

@fanfan-lucky commented on GitHub (Apr 16, 2025):

I see in Dify 1.0.0, there is not PLUGIN settings in .env, why we need to config that in 1.2.0?

@fanfan-lucky commented on GitHub (Apr 16, 2025): I see in Dify 1.0.0, there is not PLUGIN settings in .env, why we need to config that in 1.2.0?
yindo commented 2026-02-21 19:10:04 -05:00
Author
Owner
Copy Link
Copy Source

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

The need to configure PLUGIN settings in the .env file for Dify version 1.2.0 arises from the introduction of new features related to plugin management and execution. In version 1.2.0, Dify includes configurations for a Plugin Daemon, which handles plugin execution and management. This is evident from the presence of environment variables such as PLUGIN_DAEMON_PORT, PLUGIN_DAEMON_URL, PLUGIN_STORAGE_TYPE, and others related to plugin storage and execution paths. These settings were not present in version 1.0.0, indicating that plugin functionality was added in the later version, necessitating configuration in the .env file [1].

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 16, 2025): <!-- Answer --> The need to configure PLUGIN settings in the .env file for Dify version 1.2.0 arises from the introduction of new features related to plugin management and execution. In version 1.2.0, Dify includes configurations for a Plugin Daemon, which handles plugin execution and management. This is evident from the presence of environment variables such as `PLUGIN_DAEMON_PORT`, `PLUGIN_DAEMON_URL`, `PLUGIN_STORAGE_TYPE`, and others related to plugin storage and execution paths. These settings were not present in version 1.0.0, indicating that plugin functionality was added in the later version, necessitating configuration in the .env file <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker/.env.example)</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/f649a81c-d99f-40e9-84de-a7a8c936b959?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/f649a81c-d99f-40e9-84de-a7a8c936b959?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/f649a81c-d99f-40e9-84de-a7a8c936b959?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/f649a81c-d99f-40e9-84de-a7a8c936b959?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f649a81c-d99f-40e9-84de-a7a8c936b959?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/f649a81c-d99f-40e9-84de-a7a8c936b959?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f649a81c-d99f-40e9-84de-a7a8c936b959?feedback_type=other)</sup>
yindo commented 2026-02-21 19:10:04 -05:00
Author
Owner
Copy Link
Copy Source

@fanfan-lucky commented on GitHub (Apr 16, 2025):

but use 1.2.0 Dify with CentOS system, I can't add model through "OpenAI API compatible"，API log will show “core.plugin.manager.exc.PluginDaemonInternalServerError: PluginDaemonInternalServerError: no available node, plugin not found” error, and when I install "OpenAI API compatible" plugin, always need to install more than 2 times to success.

@fanfan-lucky commented on GitHub (Apr 16, 2025): but use 1.2.0 Dify with CentOS system, I can't add model through "OpenAI API compatible"，API log will show “core.plugin.manager.exc.PluginDaemonInternalServerError: PluginDaemonInternalServerError: no available node, plugin not found” error, and when I install "OpenAI API compatible" plugin, always need to install more than 2 times to success.
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 🙏 help wanted
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#12992
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?