-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot connect to xinference #3005
Comments
Hey @0xchaihu! Great to see you back here. Hope you're doing wonderfully. Let's dive into this issue together. Based on the information you've provided and the similar issues I found in the repository, it seems like the connection issue you're experiencing might be due to the network configuration between the Dify Docker container and the Xinference service. In the Docker environment, To resolve this issue, you should replace Here's a reference from the Dify documentation that explains this: en/tutorials/model-configuration/xinference.md If you've followed these steps and are still experiencing issues, it could be due to the port mapping in the docker-compose.yaml file. Ensure that you've correctly mapped the container ports to local machine ports. For example, if Xinference is running on port 9997, you should have Please let me know if this helps or if you need further assistance. Sources
|
How did you start the xinference client? |
Hi @crazywoola , thanks for your prompt reply. |
Hey, could you try accessing |
Hi @crazywoola and @takatost , after using |
Self Checks
Dify version
0.5.10
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
Add xinference embedding and rerank models but faiiled.
The IP and the models should be ok, as shown below:
✔️ Expected Behavior
It should work, the models should be able to connect to dify,
❌ Actual Behavior
get xinference model extra parameter failed, url: http://172.21.207.143:9997/v1/models/bge-base-zh, error: HTTPConnectionPool(host='172.21.207.143', port=9997): Max retries exceeded with url: /v1/models/bge-base-zh (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f49d5323070>: Failed to establish a new connection: [Errno 111] Connection refused'))
The text was updated successfully, but these errors were encountered: