Replies: 2 comments 3 replies
-
Hey @njzfw1024! 👋 I'm here to help you with any bugs, questions, or contributions you have in mind. I'm a bot designed to assist you while waiting for a human maintainer. Let's squash those bugs together! To resolve the connection timeout error when accessing a local model using Xinference on a self-hosted Docker setup with Dify version 0.6.16, ensure that the Dify container can access the Xinference endpoint. The Dify container cannot access Here are the steps to follow:
Additionally, ensure that the Xinference model extra parameters are correctly fetched and cached. The
By following these steps and ensuring the correct configuration, you should be able to resolve the connection timeout error [1][2][3][4]. |
Beta Was this translation helpful? Give feedback.
-
Self Checks
Dify version
0.6.16
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
Xinference credentials validate failed: get xinference model extra parameter failed, url: http://219.84.190.172:7855/v1/models/qw72Blora, error: HTTPConnectionPool(host='219.84.190.172', port=7855): Max retries exceeded with url: /v1/models/qw72Blora (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f2f9f1f6a40>, 'Connection to219.84.190.172 timed out. (connect timeout=10)'))
remarks: I ensure that xinference local -- host 0.0.0.0
✔️ Expected Behavior
success to access the local model
❌ Actual Behavior
failed to access the local model
Beta Was this translation helpful? Give feedback.
All reactions