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

PluginDaemonBadRequestError: read _assets: is a directory #13655

New Issue
Closed
opened 2026-02-21 19:13:11 -05:00 by yindo · 8 comments
yindo commented 2026-02-21 19:13:11 -05:00
Owner
Copy Link
Copy Source

Originally created by @eeshwarankathi on GitHub (May 7, 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.3.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. Run Docker behind corporate proxy network.
  2. Download the .difypkg file and use "Install from Local Package File" option to install the package.
  3. Seeing the below error for "http://localhost/console/api/workspaces/current/plugin/upload/pkg"
    {
    "code": "invalid_param",
    "message": "PluginDaemonBadRequestError: read _assets: is a directory",
    "status": 400
    }

✔️ Expected Behavior

the plugin is installed and ready for usage.

❌ Actual Behavior

Upload failed and plugin not installed.

Originally created by @eeshwarankathi on GitHub (May 7, 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.3.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. Run Docker behind corporate proxy network. 2. Download the .difypkg file and use "Install from Local Package File" option to install the package. 3. Seeing the below error for "http://localhost/console/api/workspaces/current/plugin/upload/pkg" { "code": "invalid_param", "message": "PluginDaemonBadRequestError: read _assets: is a directory", "status": 400 } ### ✔️ Expected Behavior the plugin is installed and ready for usage. ### ❌ Actual Behavior Upload failed and plugin not installed.
yindo added the 🐞 bug label 2026-02-21 19:13:11 -05:00
yindo closed this issue 2026-02-21 19:13:11 -05:00
yindo commented 2026-02-21 19:13:11 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 7, 2025):

Hello @eeshwarankathi! I'm Dosu, a bot here to help you with bugs, answer questions, and assist with becoming a contributor. I'm ready to support you while you wait for a human maintainer. Let's tackle this issue together!

The error message "PluginDaemonBadRequestError: read _assets: is a directory" suggests that there is an issue with the structure of the .difypkg file you are trying to upload. Specifically, it seems that the _assets directory within the package is not being handled correctly.

Here are a few steps you can take to resolve this issue:

  1. Check the _assets Directory: Ensure that the _assets directory in your plugin package is structured correctly. It should contain the necessary files rather than being an empty directory or containing unsupported files.

  2. Repackage the Plugin: If the _assets directory is structured correctly, try repackaging your plugin. Use the Dify plugin development scaffolding tool to package your plugin again, ensuring that all necessary files are included and correctly placed.

  3. Verify the Manifest: Double-check the manifest.yaml file in your plugin project to ensure that all paths and configurations are correct, especially those related to the _assets directory.

  4. Check for Updates: Make sure you are using the latest version of the Dify plugin development tools and the Dify platform itself, as updates may have fixed related issues.

If these steps do not resolve the issue, consider checking the Docker logs for more detailed error messages that might provide additional insights into what might be going wrong during the upload process.

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 (May 7, 2025): <!-- Greeting --> Hello @eeshwarankathi! I'm [Dosu](https://dosu.dev), a bot here to help you with bugs, answer questions, and assist with becoming a contributor. I'm ready to support you while you wait for a human maintainer. Let's tackle this issue together! <!-- Answer --> The error message "PluginDaemonBadRequestError: read _assets: is a directory" suggests that there is an issue with the structure of the `.difypkg` file you are trying to upload. Specifically, it seems that the `_assets` directory within the package is not being handled correctly. Here are a few steps you can take to resolve this issue: 1. **Check the `_assets` Directory**: Ensure that the `_assets` directory in your plugin package is structured correctly. It should contain the necessary files rather than being an empty directory or containing unsupported files. 2. **Repackage the Plugin**: If the `_assets` directory is structured correctly, try repackaging your plugin. Use the Dify plugin development scaffolding tool to package your plugin again, ensuring that all necessary files are included and correctly placed. 3. **Verify the Manifest**: Double-check the `manifest.yaml` file in your plugin project to ensure that all paths and configurations are correct, especially those related to the `_assets` directory. 4. **Check for Updates**: Make sure you are using the latest version of the Dify plugin development tools and the Dify platform itself, as updates may have fixed related issues. If these steps do not resolve the issue, consider checking the Docker logs for more detailed error messages that might provide additional insights into what might be going wrong during the upload process. <!-- 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/32631b13-f2a5-4926-87e6-89bbe55c87f6?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/32631b13-f2a5-4926-87e6-89bbe55c87f6?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/32631b13-f2a5-4926-87e6-89bbe55c87f6?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/32631b13-f2a5-4926-87e6-89bbe55c87f6?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/32631b13-f2a5-4926-87e6-89bbe55c87f6?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/32631b13-f2a5-4926-87e6-89bbe55c87f6?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/32631b13-f2a5-4926-87e6-89bbe55c87f6?feedback_type=other)</sup>
yindo commented 2026-02-21 19:13:11 -05:00
Author
Owner
Copy Link
Copy Source

@eeshwarankathi commented on GitHub (May 7, 2025):

@dosu
the .difypkg is downloaded from dify marketplace, so there shouldn't be a problem with the pkg

@eeshwarankathi commented on GitHub (May 7, 2025): @dosu the .difypkg is downloaded from dify marketplace, so there shouldn't be a problem with the pkg
yindo commented 2026-02-21 19:13:11 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 7, 2025):

If the .difypkg file is downloaded from the Dify Marketplace, the issue might not be with the package itself but rather with the installation process or environment. Here are a few things you can try:

  1. Check Proxy Settings: Since you're running Docker behind a corporate proxy, ensure that your proxy settings are correctly configured. This includes modifying the Squid configuration and ensuring the noProxy variable in .docker/config.json includes all necessary services [1].

  2. Disable Signature Verification: If the issue persists, try disabling plugin signature verification by adding FORCE_VERIFYING_SIGNATURE=false to your .env file and restarting your Docker containers. This can help if there are verification issues with the plugin [2].

  3. Docker Logs: Check the Docker container logs for any additional error messages that might provide more context. Use docker logs container_name to view the logs.

  4. Reinstall the Plugin: Sometimes, simply attempting to reinstall the plugin can resolve transient issues. Make sure to follow the correct steps for installing from a local file [3].

These steps should help address the issue with installing the plugin from the Marketplace.

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 (May 7, 2025): <!-- Answer --> If the `.difypkg` file is downloaded from the Dify Marketplace, the issue might not be with the package itself but rather with the installation process or environment. Here are a few things you can try: 1. **Check Proxy Settings**: Since you're running Docker behind a corporate proxy, ensure that your proxy settings are correctly configured. This includes modifying the Squid configuration and ensuring the noProxy variable in `.docker/config.json` includes all necessary services <sup>[[1]](https://github.com/langgenius/dify/issues/14472)</sup>. 2. **Disable Signature Verification**: If the issue persists, try disabling plugin signature verification by adding `FORCE_VERIFYING_SIGNATURE=false` to your `.env` file and restarting your Docker containers. This can help if there are verification issues with the plugin <sup>[[2]](https://github.com/langgenius/dify/issues/15808)</sup>. 3. **Docker Logs**: Check the Docker container logs for any additional error messages that might provide more context. Use `docker logs container_name` to view the logs. 4. **Reinstall the Plugin**: Sometimes, simply attempting to reinstall the plugin can resolve transient issues. Make sure to follow the correct steps for installing from a local file <sup>[[3]](https://github.com/crazywoola/dify-docs-mintlify/blob/main/en/plugins/quick-start/install-plugins.mdx)</sup>. These steps should help address the issue with installing the plugin from the Marketplace. <!-- 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/c00414ea-13a4-4326-a21d-b44075c5a35d?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/c00414ea-13a4-4326-a21d-b44075c5a35d?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/c00414ea-13a4-4326-a21d-b44075c5a35d?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/c00414ea-13a4-4326-a21d-b44075c5a35d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c00414ea-13a4-4326-a21d-b44075c5a35d?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/c00414ea-13a4-4326-a21d-b44075c5a35d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c00414ea-13a4-4326-a21d-b44075c5a35d?feedback_type=other)</sup>
yindo commented 2026-02-21 19:13:11 -05:00
Author
Owner
Copy Link
Copy Source

@eeshwarankathi commented on GitHub (May 7, 2025):

@dosu
is there a way to enable debug logs in "plugin_daemon" to identify the issue

@eeshwarankathi commented on GitHub (May 7, 2025): @dosu is there a way to enable debug logs in "plugin_daemon" to identify the issue
yindo commented 2026-02-21 19:13:11 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 7, 2025):

I couldn't find specific instructions for enabling debug logs in the plugin_daemon component of Dify. However, you can try checking the configuration files located in docker/docker-compose-template.yaml for any logging settings that might be adjustable [1]. Additionally, reviewing the Docker logs using docker logs container_name might provide more insights into the issue.

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 (May 7, 2025): <!-- Answer --> I couldn't find specific instructions for enabling debug logs in the `plugin_daemon` component of Dify. However, you can try checking the configuration files located in `docker/docker-compose-template.yaml` for any logging settings that might be adjustable <sup>[[1]](https://github.com/langgenius/dify/issues/14577)</sup>. Additionally, reviewing the Docker logs using `docker logs container_name` might provide more insights into the issue. <!-- 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/43f978a5-9406-45ab-85db-7a7a4f62c9b8?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/43f978a5-9406-45ab-85db-7a7a4f62c9b8?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/43f978a5-9406-45ab-85db-7a7a4f62c9b8?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/43f978a5-9406-45ab-85db-7a7a4f62c9b8?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/43f978a5-9406-45ab-85db-7a7a4f62c9b8?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/43f978a5-9406-45ab-85db-7a7a4f62c9b8?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/43f978a5-9406-45ab-85db-7a7a4f62c9b8?feedback_type=other)</sup>
yindo commented 2026-02-21 19:13:12 -05:00
Author
Owner
Copy Link
Copy Source

@bharath1992 commented on GitHub (May 7, 2025):

I have the same issue too.

@bharath1992 commented on GitHub (May 7, 2025): I have the same issue too.
yindo commented 2026-02-21 19:13:12 -05:00
Author
Owner
Copy Link
Copy Source

@frenoid commented on GitHub (May 7, 2025):

I am the seeing the same issue as @bharath1992

I am running Dify on a disconnected OpenShift cluster using the helm chart from https://github.com/BorisPolonsky/dify-helm

I am using these versions of images

  1. docker.io/langgenius/dify-api:1.3.1
  2. docker.io/langgenius/dify-web:1.3.1
  3. docker.io/langgenius/dify-sandbox:0.2.11
  4. docker.io/langgenius/dify-plugin-daemon:0.0.9-local-linux-amd64

This happens where I try to download the .difypkg files for these packages

  1. langgenius-openai_0.0.22.difypkg
  2. langgenius-bedrock_0.0.13.difypkg
  3. langgenius-anthropic_0.0.13.difypkg
  4. langgenius-ollama_0.0.6.difypkg
  5. langgenius-gemini_0.1.6.difypkg
@frenoid commented on GitHub (May 7, 2025): I am the seeing the same issue as @bharath1992 I am running Dify on a disconnected OpenShift cluster using the helm chart from [https://github.com/BorisPolonsky/dify-helm](https://github.com/BorisPolonsky/dify-helm) I am using these versions of images 1. [docker.io/langgenius/dify-api:1.3.1](http://docker.io/langgenius/dify-api:1.3.1) 2. [docker.io/langgenius/dify-web:1.3.1](http://docker.io/langgenius/dify-web:1.3.1) 3. [docker.io/langgenius/dify-sandbox:0.2.11](docker.io/langgenius/dify-sandbox:0.2.11) 4. [docker.io/langgenius/dify-plugin-daemon:0.0.9-local-linux-amd64](http://docker.io/langgenius/dify-plugin-daemon:0.0.9-local-linux-amd64) This happens where I try to download the .difypkg files for these packages 1. langgenius-openai_0.0.22.difypkg 2. langgenius-bedrock_0.0.13.difypkg 3. langgenius-anthropic_0.0.13.difypkg 4. langgenius-ollama_0.0.6.difypkg 5. langgenius-gemini_0.1.6.difypkg
yindo commented 2026-02-21 19:13:12 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 31, 2025):

Hi, @eeshwarankathi. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a PluginDaemonBadRequestError ("read _assets: is a directory") when installing a plugin from a local .difypkg file on a self-hosted Dify 1.3.1 Docker setup behind a corporate proxy.
  • The error results in a 400 Bad Request response during plugin installation.
  • You confirmed the plugin package is from the official marketplace, ruling out package corruption.
  • Other users have reported similar issues, suggesting a broader problem with plugin installation in this environment.
  • No definitive fix has been identified yet; I suggested debugging via Docker logs and configuration review.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of Dify, and if so, you can keep the discussion open by commenting here.
  • Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 31, 2025): Hi, @eeshwarankathi. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a PluginDaemonBadRequestError ("read _assets: is a directory") when installing a plugin from a local .difypkg file on a self-hosted Dify 1.3.1 Docker setup behind a corporate proxy. - The error results in a 400 Bad Request response during plugin installation. - You confirmed the plugin package is from the official marketplace, ruling out package corruption. - Other users have reported similar issues, suggesting a broader problem with plugin installation in this environment. - No definitive fix has been identified yet; I suggested debugging via Docker logs and configuration review. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of Dify, and if so, you can keep the discussion open by commenting here. - Otherwise, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
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 🐞 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#13655
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?