langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

Model Addition Fails in Silicon Flow Plugin - No Error, But Not Successful, Also have this problem #559

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

Originally created by @Reverse-Flash-Kamen on GitHub (Aug 14, 2025).

Originally assigned to: @crazywoola on GitHub.

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.5.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

This issue is reported because we really need to fix this bug.
https://github.com/langgenius/dify-official-plugins/issues/1518
https://github.com/langgenius/dify-official-plugins/issues/1517

✔️ Expected Behavior

Fix this bug

❌ Actual Behavior

No response

Originally created by @Reverse-Flash-Kamen on GitHub (Aug 14, 2025). Originally assigned to: @crazywoola on GitHub. ### 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.5.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce This issue is reported because we really need to fix this bug. https://github.com/langgenius/dify-official-plugins/issues/1518 https://github.com/langgenius/dify-official-plugins/issues/1517 ### ✔️ Expected Behavior Fix this bug ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-16 10:19:44 -05:00
yindo commented 2026-02-16 10:19:44 -05:00
Author
Owner
Copy Link
Copy Source

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

This issue with model addition failing silently in the Silicon Flow Plugin (no error, but not successful) is a known problem in self-hosted Docker setups. The root cause is often that errors from the plugin daemon or credential validation are not surfaced to the UI—so failures (like missing dependencies, network issues, or plugin version mismatches) just result in nothing happening, with no feedback.

Common causes and workarounds include: missing ML libraries (PyTorch, TensorFlow, Flax) in your Docker environment, network/MTU issues blocking pip installs, and plugin version mismatches (e.g., dify_plugin not locked to a compatible version). Solutions that have worked for others are: making sure all required libraries are installed in the plugin_daemon container, setting PIP_MIRROR_URL in your docker-compose for plugin_daemon, and matching Docker’s MTU to your VM’s MTU (e.g., set both to 1450) to avoid packet loss during dependency installation. For some plugins, locking dify_plugin to <0.2.3 in the plugin’s workflow YAML has resolved startup failures as well [source 1] [source 2].

The Dify codebase treats Silicon Flow like any other plugin provider, so any plugin can fail silently if the backend returns None/False and the UI doesn’t check for it. Improving error feedback would require changes to propagate these failures as user-visible errors.

For now, check your plugin_daemon logs for errors during model addition, confirm all dependencies are installed, and try the network and version workarounds above. If you see 500 errors in the logs, that’s a sign the plugin daemon is failing internally [source].

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Aug 14, 2025): <!-- Answer --> This issue with model addition failing silently in the Silicon Flow Plugin (no error, but not successful) is a known problem in self-hosted Docker setups. The root cause is often that errors from the plugin daemon or credential validation are not surfaced to the UI—so failures (like missing dependencies, network issues, or plugin version mismatches) just result in nothing happening, with no feedback. Common causes and workarounds include: missing ML libraries (PyTorch, TensorFlow, Flax) in your Docker environment, network/MTU issues blocking pip installs, and plugin version mismatches (e.g., dify_plugin not locked to a compatible version). Solutions that have worked for others are: making sure all required libraries are installed in the plugin_daemon container, setting `PIP_MIRROR_URL` in your docker-compose for plugin_daemon, and matching Docker’s MTU to your VM’s MTU (e.g., set both to 1450) to avoid packet loss during dependency installation. For some plugins, locking `dify_plugin` to `<0.2.3` in the plugin’s workflow YAML has resolved startup failures as well [[source 1]](https://github.com/langgenius/dify/issues/19571#issuecomment-2886553328) [[source 2]](https://github.com/langgenius/dify/issues/19632#issuecomment-2878414274). The Dify codebase treats Silicon Flow like any other plugin provider, so any plugin can fail silently if the backend returns None/False and the UI doesn’t check for it. Improving error feedback would require changes to propagate these failures as user-visible errors. For now, check your plugin_daemon logs for errors during model addition, confirm all dependencies are installed, and try the network and version workarounds above. If you see 500 errors in the logs, that’s a sign the plugin daemon is failing internally [[source]](https://github.com/langgenius/dify/issues/19653#issuecomment-2878851607). <!-- 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/bab98078-5545-40ca-9d63-249b685ece9d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/bab98078-5545-40ca-9d63-249b685ece9d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/bab98078-5545-40ca-9d63-249b685ece9d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/bab98078-5545-40ca-9d63-249b685ece9d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/bab98078-5545-40ca-9d63-249b685ece9d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/bab98078-5545-40ca-9d63-249b685ece9d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/bab98078-5545-40ca-9d63-249b685ece9d?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&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/23958)
yindo commented 2026-02-16 10:19:44 -05:00
Author
Owner
Copy Link
Copy Source

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

Issues related to plugins should use this template https://github.com/langgenius/dify-official-plugins/issues/new?template=bug_report.yml

@crazywoola commented on GitHub (Aug 14, 2025): Issues related to plugins should use this template [https://github.com/langgenius/dify-official-plugins/issues/new?template=bug_report.yml](https://github.com/langgenius/dify-official-plugins/issues/new?template=bug_report.yml)
yindo commented 2026-02-16 10:19:45 -05:00
Author
Owner
Copy Link
Copy Source

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

I do not have the access fine-tuned model, if you could provide one to help us investigate please send the credentials via email banana@dify.ai

@crazywoola commented on GitHub (Aug 14, 2025): I do not have the access fine-tuned model, if you could provide one to help us investigate please send the credentials via email banana@dify.ai
yindo commented 2026-02-16 10:19:45 -05:00
Author
Owner
Copy Link
Copy Source

@Reverse-Flash-Kamen commented on GitHub (Aug 14, 2025):

I do not have the access fine-tuned model, if you could provide one to help us investigate please send the credentials via email banana@dify.ai

alread send to yor email

@Reverse-Flash-Kamen commented on GitHub (Aug 14, 2025): > I do not have the access fine-tuned model, if you could provide one to help us investigate please send the credentials via email [banana@dify.ai](mailto:banana@dify.ai) alread send to yor email
yindo commented 2026-02-16 10:19:45 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi, @Reverse-Flash-Kamen. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a silent failure when adding models in the Silicon Flow plugin on Dify v1.5.1 self-hosted Docker.
  • The issue is linked to known problems with missing ML libraries, network/MTU issues, or plugin version mismatches.
  • Suggested troubleshooting steps included checking plugin_daemon logs and applying workarounds like setting PIP_MIRROR_URL and matching MTU values.
  • You provided fine-tuned model credentials via email for further investigation.
  • The issue remains unresolved and open pending additional investigation.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here.
  • If I don’t hear back within 5 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 31, 2025): Hi, @Reverse-Flash-Kamen. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a silent failure when adding models in the Silicon Flow plugin on Dify v1.5.1 self-hosted Docker. - The issue is linked to known problems with missing ML libraries, network/MTU issues, or plugin version mismatches. - Suggested troubleshooting steps included checking plugin_daemon logs and applying workarounds like setting PIP_MIRROR_URL and matching MTU values. - You provided fine-tuned model credentials via email for further investigation. - The issue remains unresolved and open pending additional investigation. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here. - If I don’t hear back within 5 days, I will automatically close this issue. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
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-official-plugins#559
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?