-
Notifications
You must be signed in to change notification settings - Fork 9k
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
Upgrading to 0.14.0 broke the openai_api_compatible model provider connection #11739
Comments
To resolve the "Server Unavailable Error" with the Here's how you can configure it:
This change allows the Docker container to access the service running on the host machine [1]. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
According to the url you provided, I don't think we support this if you use older version or not.
Try this instead. |
Pinpoint the problem to commit #11681, docker compose will read the system proxy env HTTP_PROXY and HTTPS_PROXY and in the case of HTTP_PROXY=127.0.0.1:7890, dify cannot access this endpoint. @crazywoola Not sure what this fix is for but for people encountering the same problem, I think you can just comment out the 2 lines added if this fix is irrelevant to you or unset the system proxy env before docker compose. |
Self Checks
Dify version
0.14.0
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
git pull
docker compose up -d
✔️ Expected Behavior
The previous version was 0.13.0 and the API worked.
❌ Actual Behavior
API Endpoint redacted for privacy.
[openai_api_compatible] Server Unavailable Error, HTTPConnectionPool(host='127.0.0.1', port=7890): Max retries exceeded with url: http://...:*/v1/chat/completions (Caused by ProxyError('Unable to connect to proxy', NewConnectionError('<urllib3.connection.HTTPConnection object at 0x79e63d47eab0>: Failed to establish a new connection: [Errno 111] Connection refused')))
The text was updated successfully, but these errors were encountered: