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

Add ranker model by Xinference plugin timeout #182

New Issue
Closed
opened 2026-02-16 10:18:22 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 10:18:22 -05:00
Owner
Copy Link
Copy Source

Originally created by @cainiaodidi on GitHub (Apr 9, 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

In the dify-api container, curl http://192.168.0.6:9997/v1/models can get model info of Xinference
Image

Then I add this model in dify as below

Image

The web doesn't raise error, but I see the log in dify-api service, it shows connect timeout。 It seems that CredentialsValidateFailedError is related to Xinference plugin not my config. How to solve it?

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @cainiaodidi on GitHub (Apr 9, 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 In the dify-api container, curl http://192.168.0.6:9997/v1/models can get model info of Xinference ![Image](https://github.com/user-attachments/assets/1a006d30-1f66-423e-b037-6a0fb703369d) Then I add this model in dify as below ![Image](https://github.com/user-attachments/assets/b2d694fd-6000-417f-9f73-2bd41771a533) The web doesn't raise error, but I see the log in dify-api service, it shows connect timeout。 It seems that CredentialsValidateFailedError is related to Xinference plugin not my config. How to solve it? ![Image](https://github.com/user-attachments/assets/0da01e89-e7b6-44c1-91e3-5f47e428eece) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-16 10:18:22 -05:00
yindo commented 2026-02-16 10:18:22 -05:00
Author
Owner
Copy Link
Copy Source

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

I found a similar unsolved discussion titled "Unable to save the model when deploying Dify using Docker, how to resolve the request timeout issue?" which might be relevant to your issue [1]. Additionally, there is a closed issue where upgrading the Xinference client to the latest version was suggested as a solution, along with checking a specific pull request [2].

For your specific issue, here are some troubleshooting steps you can try:

  1. Network Configuration: Ensure that the Dify container can access the Xinference endpoint. You can verify this by executing a curl command from within the Dify container to the Xinference server URL to check connectivity.

  2. Timeout Settings: Adjust the timeout settings in your environment configuration. You can set higher values for the connection and read timeouts to prevent timeout errors. This can be done by configuring environment variables such as HTTP_REQUEST_MAX_CONNECT_TIMEOUT and HTTP_REQUEST_MAX_READ_TIMEOUT.

  3. Docker Network: Use docker inspect to verify network connectivity between the Dify and Xinference containers. Ensure they are on the same network and can communicate with each other.

  4. Xinference Plugin: Check if there are any updates or patches available for the Xinference plugin that might address this issue.

These steps should help you diagnose and potentially resolve the connection timeout issue you're experiencing.

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 9, 2025): <!-- Answer --> I found a similar unsolved discussion titled "[Unable to save the model when deploying Dify using Docker, how to resolve the request timeout issue?](https://github.com/langgenius/dify/discussions/14714)" which might be relevant to your issue <sup>[[1]](https://github.com/langgenius/dify/discussions/14714)</sup>. Additionally, there is a closed issue where upgrading the Xinference client to the latest version was suggested as a solution, along with checking a specific pull request <sup>[[2]](https://github.com/langgenius/dify/issues/2534)</sup>. For your specific issue, here are some troubleshooting steps you can try: 1. **Network Configuration**: Ensure that the Dify container can access the Xinference endpoint. You can verify this by executing a `curl` command from within the Dify container to the Xinference server URL to check connectivity. 2. **Timeout Settings**: Adjust the timeout settings in your environment configuration. You can set higher values for the connection and read timeouts to prevent timeout errors. This can be done by configuring environment variables such as `HTTP_REQUEST_MAX_CONNECT_TIMEOUT` and `HTTP_REQUEST_MAX_READ_TIMEOUT`. 3. **Docker Network**: Use `docker inspect` to verify network connectivity between the Dify and Xinference containers. Ensure they are on the same network and can communicate with each other. 4. **Xinference Plugin**: Check if there are any updates or patches available for the Xinference plugin that might address this issue. These steps should help you diagnose and potentially resolve the connection timeout issue you're experiencing. <!-- 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/f14c5891-5f60-4561-8753-f04c32666f33?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/f14c5891-5f60-4561-8753-f04c32666f33?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/f14c5891-5f60-4561-8753-f04c32666f33?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/f14c5891-5f60-4561-8753-f04c32666f33?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f14c5891-5f60-4561-8753-f04c32666f33?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/f14c5891-5f60-4561-8753-f04c32666f33?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f14c5891-5f60-4561-8753-f04c32666f33?feedback_type=other)</sup>
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#182
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?