langgenius/dify-plugin-daemon
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugin-daemon.git synced 2026-07-21 17:25:23 -04:00
Code Issues 111 Packages Projects Releases 10 Wiki Activity

2025/04/14 12:47:51 stdio_handle.go:207: [WARN]plugin langgenius/jina_tool:0.0.7 is not active for 100.021201 #86

New Issue
Open
opened 2026-02-16 00:19:41 -05:00 by yindo · 10 comments
yindo commented 2026-02-16 00:19:41 -05:00
Owner
Copy Link
Copy Source

Originally created by @Vampxgg on GitHub (Apr 14, 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.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

2025/04/14 12:47:51 stdio_handle.go:207: [WARN]plugin langgenius/jina_tool:0.0.7 is not active for 100.021201 seconds, it may be dead
2025/04/14 12:47:51 stdio_handle.go:200: [ERROR]plugin langgenius/dalle:0.0.4 is not active for 120 seconds, it may be dead, killing and restarting it
2025/04/14 12:47:51 stdio_handle.go:134: [ERROR]plugin langgenius/dalle:0.0.4 has an error on stdout: read |0: file already closed
2025/04/14 12:47:52 stdio_handle.go:207: [WARN]plugin langgenius/siliconflow:0.0.9 is not active for 75.055883 seconds, it may be dead
2025/04/14 12:47:52 run.go:131: [ERROR]plugin langgenius/dalle:0.0.4 exited with error: signal: killed
2025/04/14 12:47:52 run.go:186: [INFO]plugin langgenius/dalle:0.0.4 stopped
2025/04/14 12:47:52 run.go:143: [INFO]plugin junjiem/mcp_see_agent:0.0.9 started
2025/04/14 12:47:53 run.go:143: [INFO]plugin junjiem/mcp_sse:0.0.8 started
2025/04/14 12:47:53 stdio_handle.go:207: [WARN]plugin stvlynn/doc:0.0.1 is not active for 65.002106 seconds, it may be dead
2025/04/14 12:47:53 stdio_handle.go:207: [WARN]plugin langgenius/siliconflow_tool:0.0.4 is not active for 70.007054 seconds, it may be dead
2025/04/14 12:47:53 stdio_handle.go:207: [WARN]plugin langgenius/volcengine_maas:0.0.10 is not active for 70.003613 seconds, it may be dead
2025/04/14 12:47:54 stdio_handle.go:207: [WARN]plugin langgenius/ollama:0.0.5 is not active for 95.000900 seconds, it may be dead
2025/04/14 12:47:54 stdio_handle.go:207: [WARN]plugin langgenius/searchapi:0.0.2 is not active for 85.000867 seconds, it may be dead
2025/04/14 12:47:54 stdio_handle.go:207: [WARN]plugin langgenius/serper:0.0.2 is not active for 80.016319 seconds, it may be dead
2025/04/14 12:47:54 stdio_handle.go:200: [ERROR]plugin langgenius/deepseek:0.0.5 is not active for 120 seconds, it may be dead, killing and restarting it
2025/04/14 12:47:54 stdio_handle.go:134: [ERROR]plugin langgenius/deepseek:0.0.5 has an error on stdout: read |0: file already closed
2025/04/14 12:47:54 run.go:143: [INFO]plugin langgenius/anthropic:0.0.13 started
2025/04/14 12:47:55 stdio_handle.go:207: [WARN]plugin langgenius/firecrawl:0.0.3 is not active for 115.007957 seconds, it may be dead
2025/04/14 12:47:55 run.go:131: [ERROR]plugin langgenius/deepseek:0.0.5 exited with error: signal: killed
2025/04/14 12:47:55 run.go:186: [INFO]plugin langgenius/deepseek:0.0.5 stopped
2025/04/14 12:47:55 stdio_handle.go:207: [WARN]plugin langgenius/openai:0.0.16 is not active for 95.032772 seconds, it may be dead
2025/04/14 12:47:55 stdio_handle.go:207: [WARN]plugin langgenius/gemini:0.1.3 is not active for 115.008419 seconds, it may be dead
2025/04/14 12:47:56 stdio_handle.go:207: [WARN]plugin langgenius/jina:0.0.6 is not active for 110.010881 seconds, it may be dead
2025/04/14 12:47:56 stdio_handle.go:207: [WARN]plugin langgenius/wikipedia:0.0.3 is not active for 70.020703 seconds, it may be dead
2025/04/14 12:47:56 stdio_handle.go:207: [WARN]plugin langgenius/jina_tool:0.0.7 is not active for 105.007274 seconds, it may be dead
2025/04/14 12:47:56 stdio_handle.go:207: [WARN]plugin langgenius/moonshot:0.0.4 is not active for 105.007192 seconds, it may be dead
2025/04/14 12:47:57 stdio_handle.go:207: [WARN]plugin langgenius/siliconflow:0.0.9 is not active for 80.032573 seconds, it may be dead
2025/04/14 12:47:57 run.go:143: [INFO]plugin langgenius/dalle:0.0.4 started
2025/04/14 12:47:58 stdio_handle.go:207: [WARN]plugin stvlynn/doc:0.0.1 is not active for 70.024738 seconds, it may be dead
2025/04/14 12:47:58 stdio_handle.go:207: [WARN]plugin langgenius/volcengine_maas:0.0.10 is not active for 75.023016 seconds, it may be dead
2025/04/14 12:47:59 stdio_handle.go:207: [WARN]plugin langgenius/ollama:0.0.5 is not active for 100.036030 seconds, it may be dead
2025/04/14 12:47:59 stdio_handle.go:207: [WARN]plugin langgenius/siliconflow_tool:0.0.4 is not active for 75.186481 seconds, it may be dead
2025/04/14 12:47:59 stdio_handle.go:207: [WARN]plugin langgenius/searchapi:0.0.2 is not active for 90.016476 seconds, it may be dead
2025/04/14 12:47:59 stdio_handle.go:207: [WARN]plugin langgenius/serper:0.0.2 is not active for 85.020987 seconds, it may be dead
2025/04/14 12:48:00 stdio_handle.go:200: [ERROR]plugin langgenius/firecrawl:0.0.3 is not active for 120 seconds, it may be dead, killing and restarting it
2025/04/14 12:48:00 stdio_handle.go:134: [ERROR]plugin langgenius/firecrawl:0.0.3 has an error on stdout: read |0: file already closed
2025/04/14 12:48:00 run.go:143: [INFO]plugin langgenius/deepseek:0.0.5 started
2025/04/14 12:48:00 stdio_handle.go:207: [WARN]plugin langgenius/openai:0.0.16 is not active for 100.002791 seconds, it may be dead
2025/04/14 12:48:00 run.go:131: [ERROR]plugin langgenius/firecrawl:0.0.3 exited with error: signal: killed
2025/04/14 12:48:00 run.go:186: [INFO]plugin langgenius/firecrawl:0.0.3 stopped
2025/04/14 12:48:00 stdio_handle.go:200: [ERROR]plugin langgenius/gemini:0.1.3 is not active for 120 seconds, it may be dead, killing and restarting it
2025/04/14 12:48:00 stdio_handle.go:134: [ERROR]plugin langgenius/gemini:0.1.3 has an error on stdout: read |0: file already closed
2025/04/14 12:48:01 stdio_handle.go:207: [WARN]plugin langgenius/jina:0.0.6 is not active for 115.018752 seconds, it may be dead
2025/04/14 12:48:01 run.go:131: [ERROR]plugin langgenius/gemini:0.1.3 exited with error: signal: killed
2025/04/14 12:48:01 run.go:186: [INFO]plugin langgenius/gemini:0.1.3 stopped
2025/04/14 12:48:01 stdio_handle.go:207: [WARN]plugin langgenius/wikipedia:0.0.3 is not active for 75.001160 seconds, it may be dead
2025/04/14 12:48:01 stdio_handle.go:207: [WARN]plugin langgenius/moonshot:0.0.4 is not active for 110.001484 seconds, it may be dead
2025/04/14 12:48:01 stdio_handle.go:207: [WARN]plugin langgenius/jina_tool:0.0.7 is not active for 110.001669 seconds, it may be dead
2025/04/14 12:48:01 stdio_handle.go:207: [WARN]plugin langgenius/siliconflow:0.0.9 is not active for 85.002651 seconds, it may be dead
2025/04/14 12:48:03 stdio_handle.go:207: [WARN]plugin stvlynn/doc:0.0.1 is not active for 75.004648 seconds, it may be dead
2025/04/14 12:48:03 stdio_handle.go:207: [WARN]plugin langgenius/siliconflow_tool:0.0.4 is not active for 80.009029 seconds, it may be dead
2025/04/14 12:48:03 stdio_handle.go:207: [WARN]plugin langgenius/volcengine_maas:0.0.10 is not active for 80.005385 seconds, it may be dead
2025/04/14 12:48:04 stdio_handle.go:207: [WARN]plugin langgenius/ollama:0.0.5 is not active for 105.000393 seconds, it may be dead
2025/04/14 12:48:04 stdio_handle.go:207: [WARN]plugin langgenius/searchapi:0.0.2 is not active for 95.000859 seconds, it may be dead
2025/04/14 12:48:04 stdio_handle.go:207: [WARN]plugin langgenius/serper:0.0.2 is not active for 90.029512 seconds, it may be dead
2025/04/14 12:48:05 stdio_handle.go:207: [WARN]plugin langgenius/openai:0.0.16 is not active for 105.000911 seconds, it may be dead
2025/04/14 12:48:05 run.go:143: [INFO]plugin langgenius/firecrawl:0.0.3 started
2025/04/14 12:48:06 stdio_handle.go:200: [ERROR]plugin langgenius/jina:0.0.6 is not active for 120 seconds, it may be dead, killing and restarting it
2025/04/14 12:48:06 stdio_handle.go:134: [ERROR]plugin langgenius/jina:0.0.6 has an error on stdout: read |0: file already closed
2025/04/14 12:48:06 run.go:143: [INFO]plugin langgenius/gemini:0.1.3 started
2025/04/14 12:48:06 stdio_handle.go:207: [WARN]plugin langgenius/wikipedia:0.0.3 is not active for 80.003566 seconds, it may be dead

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @Vampxgg on GitHub (Apr 14, 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.1.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ``` 2025/04/14 12:47:51 stdio_handle.go:207: [WARN]plugin langgenius/jina_tool:0.0.7 is not active for 100.021201 seconds, it may be dead 2025/04/14 12:47:51 stdio_handle.go:200: [ERROR]plugin langgenius/dalle:0.0.4 is not active for 120 seconds, it may be dead, killing and restarting it 2025/04/14 12:47:51 stdio_handle.go:134: [ERROR]plugin langgenius/dalle:0.0.4 has an error on stdout: read |0: file already closed 2025/04/14 12:47:52 stdio_handle.go:207: [WARN]plugin langgenius/siliconflow:0.0.9 is not active for 75.055883 seconds, it may be dead 2025/04/14 12:47:52 run.go:131: [ERROR]plugin langgenius/dalle:0.0.4 exited with error: signal: killed 2025/04/14 12:47:52 run.go:186: [INFO]plugin langgenius/dalle:0.0.4 stopped 2025/04/14 12:47:52 run.go:143: [INFO]plugin junjiem/mcp_see_agent:0.0.9 started 2025/04/14 12:47:53 run.go:143: [INFO]plugin junjiem/mcp_sse:0.0.8 started 2025/04/14 12:47:53 stdio_handle.go:207: [WARN]plugin stvlynn/doc:0.0.1 is not active for 65.002106 seconds, it may be dead 2025/04/14 12:47:53 stdio_handle.go:207: [WARN]plugin langgenius/siliconflow_tool:0.0.4 is not active for 70.007054 seconds, it may be dead 2025/04/14 12:47:53 stdio_handle.go:207: [WARN]plugin langgenius/volcengine_maas:0.0.10 is not active for 70.003613 seconds, it may be dead 2025/04/14 12:47:54 stdio_handle.go:207: [WARN]plugin langgenius/ollama:0.0.5 is not active for 95.000900 seconds, it may be dead 2025/04/14 12:47:54 stdio_handle.go:207: [WARN]plugin langgenius/searchapi:0.0.2 is not active for 85.000867 seconds, it may be dead 2025/04/14 12:47:54 stdio_handle.go:207: [WARN]plugin langgenius/serper:0.0.2 is not active for 80.016319 seconds, it may be dead 2025/04/14 12:47:54 stdio_handle.go:200: [ERROR]plugin langgenius/deepseek:0.0.5 is not active for 120 seconds, it may be dead, killing and restarting it 2025/04/14 12:47:54 stdio_handle.go:134: [ERROR]plugin langgenius/deepseek:0.0.5 has an error on stdout: read |0: file already closed 2025/04/14 12:47:54 run.go:143: [INFO]plugin langgenius/anthropic:0.0.13 started 2025/04/14 12:47:55 stdio_handle.go:207: [WARN]plugin langgenius/firecrawl:0.0.3 is not active for 115.007957 seconds, it may be dead 2025/04/14 12:47:55 run.go:131: [ERROR]plugin langgenius/deepseek:0.0.5 exited with error: signal: killed 2025/04/14 12:47:55 run.go:186: [INFO]plugin langgenius/deepseek:0.0.5 stopped 2025/04/14 12:47:55 stdio_handle.go:207: [WARN]plugin langgenius/openai:0.0.16 is not active for 95.032772 seconds, it may be dead 2025/04/14 12:47:55 stdio_handle.go:207: [WARN]plugin langgenius/gemini:0.1.3 is not active for 115.008419 seconds, it may be dead 2025/04/14 12:47:56 stdio_handle.go:207: [WARN]plugin langgenius/jina:0.0.6 is not active for 110.010881 seconds, it may be dead 2025/04/14 12:47:56 stdio_handle.go:207: [WARN]plugin langgenius/wikipedia:0.0.3 is not active for 70.020703 seconds, it may be dead 2025/04/14 12:47:56 stdio_handle.go:207: [WARN]plugin langgenius/jina_tool:0.0.7 is not active for 105.007274 seconds, it may be dead 2025/04/14 12:47:56 stdio_handle.go:207: [WARN]plugin langgenius/moonshot:0.0.4 is not active for 105.007192 seconds, it may be dead 2025/04/14 12:47:57 stdio_handle.go:207: [WARN]plugin langgenius/siliconflow:0.0.9 is not active for 80.032573 seconds, it may be dead 2025/04/14 12:47:57 run.go:143: [INFO]plugin langgenius/dalle:0.0.4 started 2025/04/14 12:47:58 stdio_handle.go:207: [WARN]plugin stvlynn/doc:0.0.1 is not active for 70.024738 seconds, it may be dead 2025/04/14 12:47:58 stdio_handle.go:207: [WARN]plugin langgenius/volcengine_maas:0.0.10 is not active for 75.023016 seconds, it may be dead 2025/04/14 12:47:59 stdio_handle.go:207: [WARN]plugin langgenius/ollama:0.0.5 is not active for 100.036030 seconds, it may be dead 2025/04/14 12:47:59 stdio_handle.go:207: [WARN]plugin langgenius/siliconflow_tool:0.0.4 is not active for 75.186481 seconds, it may be dead 2025/04/14 12:47:59 stdio_handle.go:207: [WARN]plugin langgenius/searchapi:0.0.2 is not active for 90.016476 seconds, it may be dead 2025/04/14 12:47:59 stdio_handle.go:207: [WARN]plugin langgenius/serper:0.0.2 is not active for 85.020987 seconds, it may be dead 2025/04/14 12:48:00 stdio_handle.go:200: [ERROR]plugin langgenius/firecrawl:0.0.3 is not active for 120 seconds, it may be dead, killing and restarting it 2025/04/14 12:48:00 stdio_handle.go:134: [ERROR]plugin langgenius/firecrawl:0.0.3 has an error on stdout: read |0: file already closed 2025/04/14 12:48:00 run.go:143: [INFO]plugin langgenius/deepseek:0.0.5 started 2025/04/14 12:48:00 stdio_handle.go:207: [WARN]plugin langgenius/openai:0.0.16 is not active for 100.002791 seconds, it may be dead 2025/04/14 12:48:00 run.go:131: [ERROR]plugin langgenius/firecrawl:0.0.3 exited with error: signal: killed 2025/04/14 12:48:00 run.go:186: [INFO]plugin langgenius/firecrawl:0.0.3 stopped 2025/04/14 12:48:00 stdio_handle.go:200: [ERROR]plugin langgenius/gemini:0.1.3 is not active for 120 seconds, it may be dead, killing and restarting it 2025/04/14 12:48:00 stdio_handle.go:134: [ERROR]plugin langgenius/gemini:0.1.3 has an error on stdout: read |0: file already closed 2025/04/14 12:48:01 stdio_handle.go:207: [WARN]plugin langgenius/jina:0.0.6 is not active for 115.018752 seconds, it may be dead 2025/04/14 12:48:01 run.go:131: [ERROR]plugin langgenius/gemini:0.1.3 exited with error: signal: killed 2025/04/14 12:48:01 run.go:186: [INFO]plugin langgenius/gemini:0.1.3 stopped 2025/04/14 12:48:01 stdio_handle.go:207: [WARN]plugin langgenius/wikipedia:0.0.3 is not active for 75.001160 seconds, it may be dead 2025/04/14 12:48:01 stdio_handle.go:207: [WARN]plugin langgenius/moonshot:0.0.4 is not active for 110.001484 seconds, it may be dead 2025/04/14 12:48:01 stdio_handle.go:207: [WARN]plugin langgenius/jina_tool:0.0.7 is not active for 110.001669 seconds, it may be dead 2025/04/14 12:48:01 stdio_handle.go:207: [WARN]plugin langgenius/siliconflow:0.0.9 is not active for 85.002651 seconds, it may be dead 2025/04/14 12:48:03 stdio_handle.go:207: [WARN]plugin stvlynn/doc:0.0.1 is not active for 75.004648 seconds, it may be dead 2025/04/14 12:48:03 stdio_handle.go:207: [WARN]plugin langgenius/siliconflow_tool:0.0.4 is not active for 80.009029 seconds, it may be dead 2025/04/14 12:48:03 stdio_handle.go:207: [WARN]plugin langgenius/volcengine_maas:0.0.10 is not active for 80.005385 seconds, it may be dead 2025/04/14 12:48:04 stdio_handle.go:207: [WARN]plugin langgenius/ollama:0.0.5 is not active for 105.000393 seconds, it may be dead 2025/04/14 12:48:04 stdio_handle.go:207: [WARN]plugin langgenius/searchapi:0.0.2 is not active for 95.000859 seconds, it may be dead 2025/04/14 12:48:04 stdio_handle.go:207: [WARN]plugin langgenius/serper:0.0.2 is not active for 90.029512 seconds, it may be dead 2025/04/14 12:48:05 stdio_handle.go:207: [WARN]plugin langgenius/openai:0.0.16 is not active for 105.000911 seconds, it may be dead 2025/04/14 12:48:05 run.go:143: [INFO]plugin langgenius/firecrawl:0.0.3 started 2025/04/14 12:48:06 stdio_handle.go:200: [ERROR]plugin langgenius/jina:0.0.6 is not active for 120 seconds, it may be dead, killing and restarting it 2025/04/14 12:48:06 stdio_handle.go:134: [ERROR]plugin langgenius/jina:0.0.6 has an error on stdout: read |0: file already closed 2025/04/14 12:48:06 run.go:143: [INFO]plugin langgenius/gemini:0.1.3 started 2025/04/14 12:48:06 stdio_handle.go:207: [WARN]plugin langgenius/wikipedia:0.0.3 is not active for 80.003566 seconds, it may be dead ``` ![Image](https://github.com/user-attachments/assets/4d39d4e9-c511-4537-ade9-11715b5142f2) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo commented 2026-02-16 00:19:42 -05:00
Author
Owner
Copy Link
Copy Source

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

There are known issues with plugins in Dify becoming inactive or 'dead' due to overly aggressive plugin activity tracking. This can cause plugins to be marked as inactive after a certain period, leading to restarts. Here are some steps you can take to address this issue:

  1. Upgrade Dify: Ensure you are using Dify version 1.0.1 or later, as it includes fixes for aggressive plugin activity tracking [1].

  2. Increase Plugin Execution Timeout: Modify your docker-compose.yaml file to increase the plugin execution timeout. For example:

    plugin_daemon:
  environment:
    PLUGIN_MAX_EXECUTION_TIMEOUT: 2400

  3. Remove Proxy Configurations: If you are using proxies, remove any proxy configurations from the plugin-daemon container in your docker-compose.yaml file [1].

  4. Restart Docker Containers: After making these changes, restart your Docker containers to apply the updates:

    docker compose stop
docker compose up -d

These steps should help mitigate the issue of plugins being marked as inactive or 'dead'. If the problem persists, consider checking for any specific plugin-related issues or limitations that might be affecting your setup [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 14, 2025): <!-- Answer --> There are known issues with plugins in Dify becoming inactive or 'dead' due to overly aggressive plugin activity tracking. This can cause plugins to be marked as inactive after a certain period, leading to restarts. Here are some steps you can take to address this issue: 1. **Upgrade Dify**: Ensure you are using Dify version 1.0.1 or later, as it includes fixes for aggressive plugin activity tracking <sup>[[1]](https://github.com/langgenius/dify/issues/15196)</sup>. 2. **Increase Plugin Execution Timeout**: Modify your `docker-compose.yaml` file to increase the plugin execution timeout. For example: ```yaml plugin_daemon: environment: PLUGIN_MAX_EXECUTION_TIMEOUT: 2400 ``` 3. **Remove Proxy Configurations**: If you are using proxies, remove any proxy configurations from the `plugin-daemon` container in your `docker-compose.yaml` file <sup>[[1]](https://github.com/langgenius/dify/issues/15196)</sup>. 4. **Restart Docker Containers**: After making these changes, restart your Docker containers to apply the updates: ```bash docker compose stop docker compose up -d ``` These steps should help mitigate the issue of plugins being marked as inactive or 'dead'. If the problem persists, consider checking for any specific plugin-related issues or limitations that might be affecting your setup <sup>[[1]](https://github.com/langgenius/dify/issues/15196)</sup><sup>[[2]](https://github.com/langgenius/dify/issues/14654)</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/a0a4eb94-e948-4eaa-99fd-ef5f27cc30e3?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/a0a4eb94-e948-4eaa-99fd-ef5f27cc30e3?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/a0a4eb94-e948-4eaa-99fd-ef5f27cc30e3?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/a0a4eb94-e948-4eaa-99fd-ef5f27cc30e3?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a0a4eb94-e948-4eaa-99fd-ef5f27cc30e3?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/a0a4eb94-e948-4eaa-99fd-ef5f27cc30e3?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a0a4eb94-e948-4eaa-99fd-ef5f27cc30e3?feedback_type=other)</sup>
yindo commented 2026-02-16 00:19:42 -05:00
Author
Owner
Copy Link
Copy Source

@AnoyiX commented on GitHub (Apr 14, 2025):

+1

@AnoyiX commented on GitHub (Apr 14, 2025): +1
yindo commented 2026-02-16 00:19:42 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Apr 14, 2025):

Please remove those plugins and install it again.

@crazywoola commented on GitHub (Apr 14, 2025): Please remove those plugins and install it again.
yindo commented 2026-02-16 00:19:43 -05:00
Author
Owner
Copy Link
Copy Source

@AnoyiX commented on GitHub (Apr 14, 2025):

@crazywoola How to reinstall smoothly?

@AnoyiX commented on GitHub (Apr 14, 2025): @crazywoola How to reinstall smoothly?
yindo commented 2026-02-16 00:19:43 -05:00
Author
Owner
Copy Link
Copy Source

@zhujinhua commented on GitHub (May 21, 2025):

any new about this issue? I met the same question and try the above steps but not work

Image
@zhujinhua commented on GitHub (May 21, 2025): any new about this issue? I met the same question and try the above steps but not work <img width="1812" alt="Image" src="https://github.com/user-attachments/assets/93e6bfa2-2c69-4778-a9cf-8c7d81057b89" />
yindo commented 2026-02-16 00:19:43 -05:00
Author
Owner
Copy Link
Copy Source

@Vampxgg commented on GitHub (May 22, 2025):

any new about this issue? I met the same question and try the above steps but not work这个问题有什么新进展吗？我也遇到了同样的问题，尝试了上述步骤，但不起作用。

Image

Are you using a local deployment solution?

@Vampxgg commented on GitHub (May 22, 2025): > any new about this issue? I met the same question and try the above steps but not work这个问题有什么新进展吗？我也遇到了同样的问题，尝试了上述步骤，但不起作用。 > > <img alt="Image" width="1812" src="https://private-user-images.githubusercontent.com/5045434/445961768-93e6bfa2-2c69-4778-a9cf-8c7d81057b89.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NDc5MDU5MjQsIm5iZiI6MTc0NzkwNTYyNCwicGF0aCI6Ii81MDQ1NDM0LzQ0NTk2MTc2OC05M2U2YmZhMi0yYzY5LTQ3NzgtYTljZi04YzdkODEwNTdiODkucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDUyMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTA1MjJUMDkyMDI0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NjhiZWI4ZTdkMzg4ZmFkZjQxYThhYzMxZDNhNzMyZTFhNWM0N2MyYzhjMmZlOTY0YzQ5MDdmMDg5YTNlZjEwNCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.5BC1h2wSkcz5j5oiVj2uwPbU7p89dSFJ6dOE08us49I"> Are you using a local deployment solution?
yindo commented 2026-02-16 00:19:43 -05:00
Author
Owner
Copy Link
Copy Source

@zyjfly commented on GitHub (May 23, 2025):

关于这个问题有什么新消息吗？我遇到了同样的问题并尝试了上述步骤，但没有工作这个问题有什么新进展吗？我也遇到了同样的问题，尝试了上述步骤，但不起作用。
图像

您是否正在使用本地部署解决方案？

你解决了吗 我也是这个问题

@zyjfly commented on GitHub (May 23, 2025): > > 关于这个问题有什么新消息吗？我遇到了同样的问题并尝试了上述步骤，但没有工作这个问题有什么新进展吗？我也遇到了同样的问题，尝试了上述步骤，但不起作用。 > > <img alt="图像" width="1812" src="https://private-user-images.githubusercontent.com/5045434/445961768-93e6bfa2-2c69-4778-a9cf-8c7d81057b89.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NDc5MDU5MjQsIm5iZiI6MTc0NzkwNTYyNCwicGF0aCI6Ii81MDQ1NDM0LzQ0NTk2MTc2OC05M2U2YmZhMi0yYzY5LTQ3NzgtYTljZi04YzdkODEwNTdiODkucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDUyMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTA1MjJUMDkyMDI0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NjhiZWI4ZTdkMzg4ZmFkZjQxYThhYzMxZDNhNzMyZTFhNWM0N2MyYzhjMmZlOTY0YzQ5MDdmMDg5YTNlZjEwNCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.5BC1h2wSkcz5j5oiVj2uwPbU7p89dSFJ6dOE08us49I"> > > 您是否正在使用本地部署解决方案？ 你解决了吗 我也是这个问题
yindo commented 2026-02-16 00:19:43 -05:00
Author
Owner
Copy Link
Copy Source

@Vampxgg commented on GitHub (May 25, 2025):

Please delete the plugin according to the above method, open Tsinghua's mirror source in .env, restart and reinstall the plugin

Image

关于这个问题有什么新消息吗？我遇到了同样的问题并尝试了上述步骤，但没有工作这个问题有什么新进展吗？我也遇到了同样的问题，尝试了上述步骤，但不起作用。
图像

您是否正在使用本地部署解决方案？

你解决了吗 我也是这个问题

@Vampxgg commented on GitHub (May 25, 2025): Please delete the plugin according to the above method, open Tsinghua's mirror source in .env, restart and reinstall the plugin ![Image](https://github.com/user-attachments/assets/f4f50e6d-fcea-4127-b40e-8d8c21925615) > > > 关于这个问题有什么新消息吗？我遇到了同样的问题并尝试了上述步骤，但没有工作这个问题有什么新进展吗？我也遇到了同样的问题，尝试了上述步骤，但不起作用。 > > > <img alt="图像" width="1812" src="https://private-user-images.githubusercontent.com/5045434/445961768-93e6bfa2-2c69-4778-a9cf-8c7d81057b89.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NDc5MDU5MjQsIm5iZiI6MTc0NzkwNTYyNCwicGF0aCI6Ii81MDQ1NDM0LzQ0NTk2MTc2OC05M2U2YmZhMi0yYzY5LTQ3NzgtYTljZi04YzdkODEwNTdiODkucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDUyMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTA1MjJUMDkyMDI0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NjhiZWI4ZTdkMzg4ZmFkZjQxYThhYzMxZDNhNzMyZTFhNWM0N2MyYzhjMmZlOTY0YzQ5MDdmMDg5YTNlZjEwNCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.5BC1h2wSkcz5j5oiVj2uwPbU7p89dSFJ6dOE08us49I"> > > > > > > 您是否正在使用本地部署解决方案？ > > 你解决了吗 我也是这个问题
yindo commented 2026-02-16 00:19:43 -05:00
Author
Owner
Copy Link
Copy Source

@LyleLiu666 commented on GitHub (May 28, 2025):

I also encountered the same problem, I can't figure out why we need to create a plugin center, it's too difficult to use

@LyleLiu666 commented on GitHub (May 28, 2025): I also encountered the same problem, I can't figure out why we need to create a plugin center, it's too difficult to use
yindo commented 2026-02-16 00:19:43 -05:00
Author
Owner
Copy Link
Copy Source

@sheng-chen commented on GitHub (Jul 6, 2025):

I also get the same problem

Image
@sheng-chen commented on GitHub (Jul 6, 2025): I also get the same problem <img width="1619" height="957" alt="Image" src="https://github.com/user-attachments/assets/a8e6c6d5-b031-49cc-a814-70dcb26ca587" />
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Windows
bug
cmd
documentation
enhancement
go
good first issue
plugin-daemon
pull-request
Mirrored from GitHub Pull Request
 question
No Label
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-plugin-daemon#86
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?