connection error when set up model provider

[shenhai-ran]

Self Checks

• 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.

Content

I use docker for self hosted Dify, just after initialization, I tried to setup model provider, however I got message on top right corner as connection error.

The Logs in docker show the following:

2024-08-30 11:04:56 api-1         | 2024-08-30 09:04:56,563.563 INFO [Thread-68 (process_request_thread)] [_base_client.py:1047] - Retrying request to /chat/completions in 0.759598 seconds
2024-08-30 11:04:57 api-1         | 2024-08-30 09:04:57,679.679 INFO [Thread-68 (process_request_thread)] [_internal.py:97] - 172.18.0.9 - - [30/Aug/2024 09:04:57] "POST /console/api/workspaces/current/model-providers/openai HTTP/1.1" 400 -
2024-08-30 11:04:57 nginx-1       | 172.18.0.1 - - [30/Aug/2024:09:04:57 +0000] "POST /console/api/workspaces/current/model-providers/openai HTTP/1.1" 400 87 "http://localhost/apps" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36 Edg/127.0.0.0" "-"

I am inside corporation network, with a self signed certificate. I don't know if this is related.
I also got error message from checking updates because of this:

2024-08-30 10:47:10 api-1         | 2024-08-30 08:47:10,459.459 WARNING [Thread-6 (process_request_thread)] [version.py:36] - Check update version error: HTTPSConnectionPool(host='updates.dify.ai', port=443): Max retries exceeded with url: /?current_version=0.7.2 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1007)'))).

[liangnet]

you should add HTTP_PROXY / HTTP_PROXY in docker-compose.yaml. for example,

x-shared-env: &shared-api-worker-env
HTTPS_PROXY: http://192.168.0.1:1234
HTTP_PROXY: http://192.168.0.1:1234
...

then, they will be imported in environment sections of such yaml. In addition, you will face another problem that dify cannot write data to vector database weaviate!!! don't worry, you need to add
NO_PROXY: localhost,127.0.0.1,weaviate
to two sections, like this

services:
api:
environment:
...
NO_PROXY: localhost,127.0.0.1,weaviate

worker:
environment:
...
NO_PROXY: localhost,127.0.0.1,weaviate

[rosetogun]

1. Using Docker locally with Dify 0.10.2, an error message is displayed when setting up the model provider:
   2024-11-04 14:25:09,199.199 WARNING [Dummy-1] [version.py:36] - Check update version error: HTTPSConnectionPool(host='updates.dify.ai', port=443): Max retries exceeded with url: /?current_version=0.10.2 (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7ff3f8bf9900>: Failed to resolve 'updates.dify.ai' ([Errno -3] Temporary failure in name resolution)")).
   2024-11-04 14:25:49,111.111 ERROR [Dummy-2] [http_request.py:230] - HTTPSConnectionPool(host='dashscope.aliyuncs.com', port=443): Max retries exceeded with url: /api/v1/services/aigc/text-generation/generation (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7ff3f8c5ee30>: Failed to resolve 'dashscope.aliyuncs.com' ([Errno -3] Temporary failure in name resolution)"))。
2. add HTTP_PROXY / HTTP_PROXY in docker-compose.yaml.。Due to the Docker network being set to an internal network, the configured HTTP_PROXY is unreachable, resulting in a new error.：
   Unable to create default JumpStart SageMaker Session due to the following error: Failed to connect to proxy URL: "http://192.168.2.8:10809".
   2024-11-04 14:52:50,879.879 WARNING [Dummy-1] [version.py:36] - Check update version error: HTTPSConnectionPool(host='updates.dify.ai', port=443): Max retries exceeded with url: /?current_version=0.10.2 (Caused by ProxyError('Unable to connect to proxy', ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7fd5554b5270>, 'Connection to 192.168.2.8 timed out. (connect timeout=None)'))).

[shenhai-ran]

Hi,

Thanks for your feedback, however, I think my issue is not regarding proxy, but rather a self signed certificate. Do you know how to include that in the configuration?

Thanks again.

[peng-wei-51899]

Liangnet is essentially correct, but the specific writing method needs attention. My situation involves upgrading Dify from 0.7.x to 0.11.x. After fetching the new versions through Git, I edited the docker-compose.yaml configuration file. The configuration code is similar to the following format:

Finally, when editing the YAML file, be very careful with the use of the space bar and tab key. If you encounter an error like "yaml: line 301: did not find expected key," please check the format of the content you just edited.