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

LLM's tools-SillicnFlow #331

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

Originally created by @patrickstar231 on GitHub (Jun 1, 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.4.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1.SillicnFlow's tools cannot be installed via the Market and require manual download and installation.​​
​​2.After installation, adding the model shows success, but the corresponding model does not appear and cannot be selected.​​

✔️ Expected Behavior

No response

❌ Actual Behavior

1.SillicnFlow's tools cannot be installed via the Market and require manual download and installation.​​
​​2.After installation, adding the model shows success, but the corresponding model does not appear and cannot be selected.​​

Originally created by @patrickstar231 on GitHub (Jun 1, 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.4.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1.SillicnFlow's tools cannot be installed via the Market and require manual download and installation.​​ ​​2.After installation, adding the model shows success, but the corresponding model does not appear and cannot be selected.​​ ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior 1.SillicnFlow's tools cannot be installed via the Market and require manual download and installation.​​ ​​2.After installation, adding the model shows success, but the corresponding model does not appear and cannot be selected.​​
yindo closed this issue 2026-02-16 10:19:01 -05:00
yindo commented 2026-02-16 10:19:02 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 1, 2025):

There are several known issues and troubleshooting steps for SillicnFlow's tools not appearing after manual installation in a self-hosted Dify (Docker) environment:

  1. Network Configuration: If your Docker setup uses localhost or 127.0.0.1 for service endpoints, models and plugins may not be accessible. Use the internal IP address or http://host.docker.internal for Docker connectivity. Also, ensure that PLUGIN_DAEMON_URL is set to the correct host and port (e.g., http://host.docker.internal:5002), and that SANDBOX_ENABLE_NETWORK is set to true to allow network access for plugins and models [source].

  2. Provider Registration: The error where the SillicnFlow provider or model does not appear is often due to the provider not being registered or defined correctly. Make sure the langgenius/siliconflow_tool/siliconflow provider is registered in your Dify codebase. Built-in tool providers are typically defined in the BuiltinToolProvider class. Also, verify that all necessary configuration files (such as YAML files defining the provider's models and properties) are present and correctly set up [source].

  3. Credential Validation: If you see errors like "Credentials validation failed with status code 403", this indicates an authentication error with the SillicnFlow API key. Double-check that your API key is valid and has the required permissions. The validation process involves a GET request to the SillicnFlow API endpoint with your key; a non-200 response will prevent the model from being registered [source].

  4. Model Configuration and Filtering: Dify dynamically discovers and registers models and tools based on provider/plugin managers and configuration. If a model is not visible, it could be filtered out by environment variables or configuration settings (such as POSITION_PROVIDER_INCLUDES or POSITION_PROVIDER_EXCLUDES in your .env file), or due to missing/incomplete registration or schema errors [source].

  5. Manual Plugin Installation: If you installed the tool manually, ensure you followed the correct process: package the plugin as a .difypkg file and use the "Install via Local File" option in the Dify web interface. If the plugin still does not appear, check the Docker logs for errors and try reinstalling [source].

  6. Version Compatibility: Some users have reported that updating Dify to a newer version resolved issues with SillicnFlow models not appearing, though others have seen the issue persist even on recent versions. If you are not on the latest 1.4.x release, consider updating [source].

If you have checked all of the above and the model still does not appear, review your Docker logs for errors related to plugin loading, provider registration, or credential validation. These logs often provide clues about what step is failing.

If you need more targeted help, please share any error messages from your logs or screenshots of your provider/model configuration screens.

To reply, just mention my name @dosu.

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

@dosubot[bot] commented on GitHub (Jun 1, 2025): <!-- Answer --> There are several known issues and troubleshooting steps for SillicnFlow's tools not appearing after manual installation in a self-hosted Dify (Docker) environment: 1. **Network Configuration**: If your Docker setup uses `localhost` or `127.0.0.1` for service endpoints, models and plugins may not be accessible. Use the internal IP address or `http://host.docker.internal` for Docker connectivity. Also, ensure that `PLUGIN_DAEMON_URL` is set to the correct host and port (e.g., `http://host.docker.internal:5002`), and that `SANDBOX_ENABLE_NETWORK` is set to `true` to allow network access for plugins and models [[source]](https://github.com/langgenius/dify/issues/20325). 2. **Provider Registration**: The error where the SillicnFlow provider or model does not appear is often due to the provider not being registered or defined correctly. Make sure the `langgenius/siliconflow_tool/siliconflow` provider is registered in your Dify codebase. Built-in tool providers are typically defined in the `BuiltinToolProvider` class. Also, verify that all necessary configuration files (such as YAML files defining the provider's models and properties) are present and correctly set up [[source]](https://github.com/langgenius/dify/issues/14614). 3. **Credential Validation**: If you see errors like "Credentials validation failed with status code 403", this indicates an authentication error with the SillicnFlow API key. Double-check that your API key is valid and has the required permissions. The validation process involves a GET request to the SillicnFlow API endpoint with your key; a non-200 response will prevent the model from being registered [[source]](https://github.com/langgenius/dify/issues/11844). 4. **Model Configuration and Filtering**: Dify dynamically discovers and registers models and tools based on provider/plugin managers and configuration. If a model is not visible, it could be filtered out by environment variables or configuration settings (such as `POSITION_PROVIDER_INCLUDES` or `POSITION_PROVIDER_EXCLUDES` in your `.env` file), or due to missing/incomplete registration or schema errors [[source]](https://github.com/langgenius/dify/issues/13276). 5. **Manual Plugin Installation**: If you installed the tool manually, ensure you followed the correct process: package the plugin as a `.difypkg` file and use the "Install via Local File" option in the Dify web interface. If the plugin still does not appear, check the Docker logs for errors and try reinstalling [[source]](https://github.com/langgenius/dify/issues/16153). 6. **Version Compatibility**: Some users have reported that updating Dify to a newer version resolved issues with SillicnFlow models not appearing, though others have seen the issue persist even on recent versions. If you are not on the latest 1.4.x release, consider updating [[source]](https://github.com/langgenius/dify/issues/11844). If you have checked all of the above and the model still does not appear, review your Docker logs for errors related to plugin loading, provider registration, or credential validation. These logs often provide clues about what step is failing. If you need more targeted help, please share any error messages from your logs or screenshots of your provider/model configuration screens. <!-- Dosu Comment Footer --> *To reply, just mention my name [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/04ba0392-3bca-4d0d-85f5-15829fe51d65?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/04ba0392-3bca-4d0d-85f5-15829fe51d65?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/04ba0392-3bca-4d0d-85f5-15829fe51d65?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/04ba0392-3bca-4d0d-85f5-15829fe51d65?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/04ba0392-3bca-4d0d-85f5-15829fe51d65?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/04ba0392-3bca-4d0d-85f5-15829fe51d65?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/04ba0392-3bca-4d0d-85f5-15829fe51d65?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/20544)
yindo commented 2026-02-16 10:19:02 -05:00
Author
Owner
Copy Link
Copy Source

@jackalcooper commented on GitHub (Jun 10, 2025):

Image

Is this related?

@jackalcooper commented on GitHub (Jun 10, 2025): <img width="375" alt="Image" src="https://github.com/user-attachments/assets/4d66926f-09ab-4fc8-a7cb-43669d8f2a90" /> Is this related?
yindo commented 2026-02-16 10:19:02 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi, @patrickstar231. 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 that SiliconFlow's tools cannot be installed via the Market on Dify v1.4.1 self-hosted Docker, requiring manual installation.
  • Despite successful addition, the models do not appear as expected.
  • Troubleshooting steps were provided around Docker network settings, provider registration, credential validation, model filtering, manual plugin installation, and version compatibility.
  • Another user shared a screenshot that might be related to the issue.
  • The core challenge remains ensuring correct configuration and environment setup to make the models visible.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here to keep the discussion open.
  • 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 20, 2025): Hi, @patrickstar231. 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 that SiliconFlow's tools cannot be installed via the Market on Dify v1.4.1 self-hosted Docker, requiring manual installation. - Despite successful addition, the models do not appear as expected. - Troubleshooting steps were provided around Docker network settings, provider registration, credential validation, model filtering, manual plugin installation, and version compatibility. - Another user shared a screenshot that might be related to the issue. - The core challenge remains ensuring correct configuration and environment setup to make the models visible. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here to keep the discussion open. - 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#331
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?