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

Markdown Exporter plugin fails to intall #21000

New Issue
Closed
opened 2026-02-21 20:10:12 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 20:10:12 -05:00
Owner
Copy Link
Copy Source

Originally created by @Akrishtsingh1997 on GitHub (Dec 12, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.7.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

While trying to install and initialize the Markdown Exporter plugin
(bowenliang123/md_exporter:2.2.0) inside Dify, I consistently receive the following error:

init environment for plugin bowenliang123/md_exporter:2.2.0 failed too many times,
you should consider the package is corrupted

The plugin never completes initialization and cannot be used.

✔️ Expected Behavior

The plugin should:

Download the plugin (bowenliang123/md_exporter:2.2.0)

Initialize the plugin environment

Become available in the Tools list without errors

❌ Actual Behavior

Plugin repeatedly fails to install

Dify reports the environment setup failed multiple times

Plugin cannot be used in workflows

Originally created by @Akrishtsingh1997 on GitHub (Dec 12, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.7.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce While trying to install and initialize the Markdown Exporter plugin (bowenliang123/md_exporter:2.2.0) inside Dify, I consistently receive the following error: init environment for plugin bowenliang123/md_exporter:2.2.0 failed too many times, you should consider the package is corrupted The plugin never completes initialization and cannot be used. ### ✔️ Expected Behavior The plugin should: Download the plugin (bowenliang123/md_exporter:2.2.0) Initialize the plugin environment Become available in the Tools list without errors ### ❌ Actual Behavior Plugin repeatedly fails to install Dify reports the environment setup failed multiple times Plugin cannot be used in workflows
yindo added the 🐞 bug🌚 invalidoutdated labels 2026-02-21 20:10:12 -05:00
yindo closed this issue 2026-02-21 20:10:12 -05:00
yindo commented 2026-02-21 20:10:12 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 12, 2025):

Hi @Akrishtsingh1997! I'm Dosu and I’m helping the dify team.

This error usually means the plugin daemon failed to set up the environment, often due to network timeouts, dependency download issues, or packaging problems. Here are the most effective steps to troubleshoot:

  1. Check logs for details: run docker compose logs plugin_daemon and docker compose logs api. Set LOG_LEVEL=DEBUG and ENABLE_REQUEST_LOGGING=True in your .env to get more info.
  2. If you see errors about dependency downloads (like PyPI timeouts), increase the HTTP timeout by setting UV_HTTP_TIMEOUT=120s (or higher) in your plugin_daemon environment. You can also set a PyPI mirror with PIP_MIRROR_URL=https://pypi.tuna.tsinghua.edu.cn/simple for faster, more reliable downloads—especially if you’re in a region with slow PyPI access. See example
  3. Adjust Docker network settings if you suspect connectivity issues: set the MTU to match your host (e.g., 1450), or use network_mode: host for the plugin_daemon service. Restart the container after making changes.
  4. Increase the Python environment initialization timeout by adding PYTHON_ENV_INIT_TIMEOUT: 320 to your plugin_daemon service in docker-compose.yaml.
  5. If you keep seeing "package is corrupted" or "maximum retries" errors, try downloading the .difypkg file for the plugin from the Dify marketplace and install it manually via the web interface.
  6. As a last resort, disable signature verification by adding FORCE_VERIFYING_SIGNATURE=false to your .env and restarting Dify.

If none of these work, collect and share the detailed logs from both the main app and plugin_daemon during the failed install attempt. This will help pinpoint whether it’s a network, dependency, or packaging issue. Similar problems have been reported for other plugins and usually require manual troubleshooting and log analysis. Reference

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Dec 12, 2025): <!-- Greeting --> Hi @Akrishtsingh1997! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This error usually means the plugin daemon failed to set up the environment, often due to network timeouts, dependency download issues, or packaging problems. Here are the most effective steps to troubleshoot: 1. Check logs for details: run `docker compose logs plugin_daemon` and `docker compose logs api`. Set `LOG_LEVEL=DEBUG` and `ENABLE_REQUEST_LOGGING=True` in your `.env` to get more info. 2. If you see errors about dependency downloads (like PyPI timeouts), increase the HTTP timeout by setting `UV_HTTP_TIMEOUT=120s` (or higher) in your plugin_daemon environment. You can also set a PyPI mirror with `PIP_MIRROR_URL=https://pypi.tuna.tsinghua.edu.cn/simple` for faster, more reliable downloads—especially if you’re in a region with slow PyPI access. [See example](https://github.com/langgenius/dify-official-plugins/issues/2086) 3. Adjust Docker network settings if you suspect connectivity issues: set the MTU to match your host (e.g., 1450), or use `network_mode: host` for the plugin_daemon service. Restart the container after making changes. 4. Increase the Python environment initialization timeout by adding `PYTHON_ENV_INIT_TIMEOUT: 320` to your `plugin_daemon` service in `docker-compose.yaml`. 5. If you keep seeing "package is corrupted" or "maximum retries" errors, try downloading the `.difypkg` file for the plugin from the Dify marketplace and install it manually via the web interface. 6. As a last resort, disable signature verification by adding `FORCE_VERIFYING_SIGNATURE=false` to your `.env` and restarting Dify. If none of these work, collect and share the detailed logs from both the main app and plugin_daemon during the failed install attempt. This will help pinpoint whether it’s a network, dependency, or packaging issue. Similar problems have been reported for other plugins and usually require manual troubleshooting and log analysis. [Reference](https://github.com/langgenius/dify-official-plugins/issues/2086) <!-- 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/7c984d49-5883-449a-901d-66f3b01036d1?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/7c984d49-5883-449a-901d-66f3b01036d1?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/7c984d49-5883-449a-901d-66f3b01036d1?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/7c984d49-5883-449a-901d-66f3b01036d1?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7c984d49-5883-449a-901d-66f3b01036d1?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/7c984d49-5883-449a-901d-66f3b01036d1?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/7c984d49-5883-449a-901d-66f3b01036d1?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20error%20usually%20means%20the%20plugin%20daemon%20failed%20to%20set%20up%20the%20environment%2C%20often%20due%20to%20network%20timeouts%2C%20dependency%20download%20issues%2C%20or%20packaging%20problems.%20Here%20are%20the%20most%20effective%20steps%20to%20troubleshoot%3A%0A%0A1.%20Check%20logs%20for%20details%3A%20run%20%60docker%20compose%20logs%20plugin_daemon%60%20and%20%60docker%20compose%20logs%20api%60.%20Set%20%60LOG_LEVEL%3DDEBUG%60%20and%20%60ENABLE_REQUEST_LOGGING%3DTrue%60%20in%20your%20%60.env%60%20to%20get%20more%20info.%0A2.%20If%20you%20see%20errors%20about%20dependency%20downloads%20%28like%20PyPI%20timeouts%29%2C%20increase%20the%20HTTP%20timeout%20by%20setting%20%60UV_HTTP_TIMEOUT%3D120s%60%20%28or%20higher%29%20in%20your%20plugin_daemon%20environment.%20You%20can%20also%20set%20a%20PyPI%20mirror%20with%20%60PIP_MIRROR_URL%3Dhttps%3A//pypi.tuna.tsinghua.edu.cn/simple%60%20for%20faster%2C%20more%20reliable%20downloads%E2%80%94especially%20if%20you%E2%80%99re%20in%20a%20region%20with%20slow%20PyPI%20access.%20%5BSee%20example%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/2086%29%0A3.%20Adjust%20Docker%20network%20settings%20if%20you%20suspect%20connectivity%20issues%3A%20set%20the%20MTU%20to%20match%20your%20host%20%28e.g.%2C%201450%29%2C%20or%20use%20%60network_mode%3A%20host%60%20for%20the%20plugin_daemon%20service.%20Restart%20the%20container%20after%20making%20changes.%0A4.%20Increase%20the%20Python%20environment%20initialization%20timeout%20by%20adding%20%60PYTHON_ENV_INIT_TIMEOUT%3A%20320%60%20to%20your%20%60plugin_daemon%60%20service%20in%20%60docker-compose.yaml%60.%0A5.%20If%20you%20keep%20seeing%20%22package%20is%20corrupted%22%20or%20%22maximum%20retries%22%20errors%2C%20try%20downloading%20the%20%60.difypkg%60%20file%20for%20the%20plugin%20from%20the%20Dify%20marketplace%20and%20install%20it%20manually%20via%20the%20web%20interface.%0A6.%20As%20a%20last%20resort%2C%20disable%20signature%20verification%20by%20adding%20%60FORCE_VERIFYING_SIGNATURE%3Dfalse%60%20to%20your%20%60.env%60%20and%20restarting%20Dify.%0A%0AIf%20none%20of%20these%20work%2C%20collect%20and%20share%20the%20detailed%20logs%20from%20both%20the%20main%20app%20and%20plugin_daemon%20during%20the%20failed%20install%20attempt.%20This%20will%20help%20pinpoint%20whether%20it%E2%80%99s%20a%20network%2C%20dependency%2C%20or%20packaging%20issue.%20Similar%20problems%20have%20been%20reported%20for%20other%20plugins%20and%20usually%20require%20manual%20troubleshooting%20and%20log%20analysis.%20%5BReference%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/2086%29)&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/29566)
yindo commented 2026-02-21 20:10:12 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 12, 2025):

Issues related to the plugins should not submit to this repo .

@crazywoola commented on GitHub (Dec 12, 2025): Issues related to the plugins should not submit to this repo .
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 outdated 🌚 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#21000
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?