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

After changing my STORAGE_TYPE and PLUGIN_STORAGE_TYPE to s3 i'm getting errors plugin not found #15118

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

Originally created by @mendybraun on GitHub (Jul 4, 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.5.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I have updated my STORAGE_TYPE and PLUGIN_STORAGE_TYPE to s3 i'm getting errors plugin not found

  File "/app/api/core/model_runtime/model_providers/__base/ai_model.py", line 159, in get_model_schema
    schema = plugin_model_manager.get_model_schema(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/api/core/plugin/impl/model.py", line 69, in get_model_schema
    for resp in response:
                ^^^^^^^^
  File "/app/api/core/plugin/impl/base.py", line 211, in _request_with_plugin_daemon_response_stream
    self._handle_plugin_daemon_error(error.error_type, error.message)
  File "/app/api/core/plugin/impl/base.py", line 247, in _handle_plugin_daemon_error
    raise PluginDaemonInternalServerError(description=message)
core.plugin.impl.exc.PluginDaemonInternalServerError: PluginDaemonInternalServerError: no available node, plugin not found

✔️ Expected Behavior

it should migrate to s3

❌ Actual Behavior

No response

Originally created by @mendybraun on GitHub (Jul 4, 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.5.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I have updated my STORAGE_TYPE and PLUGIN_STORAGE_TYPE to s3 i'm getting errors plugin not found ``` File "/app/api/core/model_runtime/model_providers/__base/ai_model.py", line 159, in get_model_schema schema = plugin_model_manager.get_model_schema( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/core/plugin/impl/model.py", line 69, in get_model_schema for resp in response: ^^^^^^^^ File "/app/api/core/plugin/impl/base.py", line 211, in _request_with_plugin_daemon_response_stream self._handle_plugin_daemon_error(error.error_type, error.message) File "/app/api/core/plugin/impl/base.py", line 247, in _handle_plugin_daemon_error raise PluginDaemonInternalServerError(description=message) core.plugin.impl.exc.PluginDaemonInternalServerError: PluginDaemonInternalServerError: no available node, plugin not found ``` ### ✔️ Expected Behavior it should migrate to s3 ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🌚 invalid labels 2026-02-21 19:20:15 -05:00
yindo closed this issue 2026-02-21 19:20:15 -05:00
yindo commented 2026-02-21 19:20:16 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 4, 2025):

The "plugin not found" error after switching STORAGE_TYPE and PLUGIN_STORAGE_TYPE to S3 is usually caused by missing or misconfigured S3-related environment variables, or by plugins not being present in the S3 bucket in the expected structure.

For Dify 1.5.1 with Docker, make sure you have set all the following environment variables, either in your .env file or in your docker-compose.yaml:

  • S3_ENDPOINT
  • S3_REGION (default: us-east-1)
  • S3_BUCKET_NAME (default: difyai)
  • S3_ACCESS_KEY
  • S3_SECRET_KEY
  • S3_USE_AWS_MANAGED_IAM (should be false unless you use AWS IAM)
  • PLUGIN_S3_USE_AWS_MANAGED_IAM=false
  • PLUGIN_S3_USE_PATH_STYLE=false
  • PLUGIN_S3_ENDPOINT (if different from S3_ENDPOINT)
  • PLUGIN_AWS_REGION (should match S3_REGION)

If any of these are missing or not set to the correct value, the plugin daemon may fail to connect to S3 or parse the environment, resulting in "plugin not found" errors. This is especially important for the PLUGIN_S3_USE_AWS_MANAGED_IAM and PLUGIN_S3_USE_PATH_STYLE variables, which must be explicitly set to false to avoid parsing errors and plugin discovery failures [1] [2] [3] [4] [5].

Also, ensure that your plugins are actually present in the S3 bucket and accessible with the credentials you provided. If you migrated from local storage, you may need to manually upload your plugins to the correct S3 location.

Recent changes in Docker defaults mean that S3_USE_AWS and PLUGIN_S3_USE_AWS are now set to false by default, but you should still check your environment to be sure [6] [7].

If you have confirmed all variables and the bucket contents, but still see the error, check your Docker network configuration and make sure internal service URLs (like INTERNAL_FILES_URL) are set correctly for plugin file access [8].

If you need more details on the expected S3 bucket structure for plugins or how to migrate plugins from local to S3, let me know!

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Jul 4, 2025): <!-- Answer --> The "plugin not found" error after switching STORAGE_TYPE and PLUGIN_STORAGE_TYPE to S3 is usually caused by missing or misconfigured S3-related environment variables, or by plugins not being present in the S3 bucket in the expected structure. For Dify 1.5.1 with Docker, make sure you have set all the following environment variables, either in your `.env` file or in your `docker-compose.yaml`: - S3_ENDPOINT - S3_REGION (default: us-east-1) - S3_BUCKET_NAME (default: difyai) - S3_ACCESS_KEY - S3_SECRET_KEY - S3_USE_AWS_MANAGED_IAM (should be false unless you use AWS IAM) - PLUGIN_S3_USE_AWS_MANAGED_IAM=false - PLUGIN_S3_USE_PATH_STYLE=false - PLUGIN_S3_ENDPOINT (if different from S3_ENDPOINT) - PLUGIN_AWS_REGION (should match S3_REGION) If any of these are missing or not set to the correct value, the plugin daemon may fail to connect to S3 or parse the environment, resulting in "plugin not found" errors. This is especially important for the `PLUGIN_S3_USE_AWS_MANAGED_IAM` and `PLUGIN_S3_USE_PATH_STYLE` variables, which must be explicitly set to `false` to avoid parsing errors and plugin discovery failures [[1]](https://github.com/langgenius/dify/issues/17788) [[2]](https://github.com/langgenius/dify/issues/18621) [[3]](https://github.com/langgenius/dify/issues/17677) [[4]](https://github.com/langgenius/dify/issues/18620) [[5]](https://github.com/langgenius/dify/issues/17725). Also, ensure that your plugins are actually present in the S3 bucket and accessible with the credentials you provided. If you migrated from local storage, you may need to manually upload your plugins to the correct S3 location. Recent changes in Docker defaults mean that S3_USE_AWS and PLUGIN_S3_USE_AWS are now set to `false` by default, but you should still check your environment to be sure [[6]](https://github.com/langgenius/dify/pull/21841) [[7]](https://github.com/langgenius/dify/pull/21152). If you have confirmed all variables and the bucket contents, but still see the error, check your Docker network configuration and make sure internal service URLs (like `INTERNAL_FILES_URL`) are set correctly for plugin file access [[8]](https://github.com/langgenius/dify/pull/21382). If you need more details on the expected S3 bucket structure for plugins or how to migrate plugins from local to S3, let me know! <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/6c759fc9-9f9f-40ca-b499-c5807fb5227a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/6c759fc9-9f9f-40ca-b499-c5807fb5227a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/6c759fc9-9f9f-40ca-b499-c5807fb5227a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/6c759fc9-9f9f-40ca-b499-c5807fb5227a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/6c759fc9-9f9f-40ca-b499-c5807fb5227a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/6c759fc9-9f9f-40ca-b499-c5807fb5227a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/6c759fc9-9f9f-40ca-b499-c5807fb5227a?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/21912)
yindo commented 2026-02-21 19:20:16 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 4, 2025):

By changing the STORAGE_TYPE will migrate to the s3 automatically. You need to reinstall the missing packages.

@crazywoola commented on GitHub (Jul 4, 2025): By changing the STORAGE_TYPE will migrate to the s3 automatically. You need to reinstall the missing packages.
yindo commented 2026-02-21 19:20:16 -05:00
Author
Owner
Copy Link
Copy Source

@mendybraun commented on GitHub (Jul 4, 2025):

@crazywoola which missing packages?

@mendybraun commented on GitHub (Jul 4, 2025): @crazywoola which missing packages?
yindo commented 2026-02-21 19:20:16 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 7, 2025):

The plugins.

@crazywoola commented on GitHub (Jul 7, 2025): The plugins.
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 🌚 invalid 🐞 bug
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#15118
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?