'Connection Error' when setup OpenAI on Model Provider after upgrading to 0.14.1 #11839

Ynewtime · 2024-12-19T09:59:14Z

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

0.14.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Same network configuration (Chinese Mainland with Clash Proxy), same environment (WSL2 + Docker Desktop), one was launched from 0.13.2 and the other launched from 0.14.1:

Notice that the app launched from 0.13.2 can setup OpenAI (and chat) successfully, but the app launched from 0.14.1 cannot even setup OpenAI with error: 'Connection Error' as shared screenshots.

Environment: WSL2 2.3.26.0 + Docker Desktop v4.37.1
Network: China Mainland with Clash Proxy
Reproduction:

for 0.13.2:

git clone https://github.com/langgenius/dify.git dify-0132  # clone the latest repo
git checkout 0ff8bd2  # switch to 0.13.2
cd docker
cp .env.example .env
docker compose -p dify-0132 up -d

for 0.14.1

git clone https://github.com/langgenius/dify.git dify-0141  # clone the latest repo
cd docker
cp .env.example .env
# modify the EXPOSE_NGINX_PORT and EXPOSE_NGINX_SSL_PORT env to 3000 and 3001
docker compose -p dify-0141 up -d

...both apps can start up normally as per the reproduction steps above with no other configurations differed. Only the error happens in OpenAI setup of 0.14.1.

✔️ Expected Behavior

0.14.1 seems to have proxy configuration enhanced, as per this #11681, though it did introduces connection error.

Expect the app to behave as the same as 0.13.2 version.

❌ Actual Behavior

0.14.1: OpenAI and Claude API cannot be setup succesfully, connection error.

dosubot · 2024-12-19T10:03:52Z

Hey @Ynewtime! 👋 I'm here to help you with your Dify issue. I can assist with bug solving, answering questions, and guide you on becoming a contributor. Let's dive into resolving the issue together!

The 'Connection Error' you're experiencing when setting up OpenAI on the Model Provider after upgrading to version 0.14.1 is likely due to changes in how Docker Compose handles proxy settings in this version. In Dify 0.14.0 and likely 0.14.1, Docker Compose reads the system proxy environment variables (HTTP_PROXY and HTTPS_PROXY), which can interfere with API connections if these variables are set to values like 127.0.0.1:7890.

To resolve this issue, you can try the following:

Unset the system proxy environment variables (HTTP_PROXY and HTTPS_PROXY) on the Dify host machine before running Docker Compose.
Comment out the proxy-related lines added in commit fix: fix proxy for docker #11681 in the Docker Compose configuration if the proxy settings are not needed.

These steps should help establish the connection successfully, similar to how it worked in version 0.13.2 ^[1].

To continue talking to Dosu, mention @dosu.

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

Ynewtime · 2024-12-19T10:11:18Z

To resolve this issue, you can try the following:

Unset the system proxy environment variables (HTTP_PROXY and HTTPS_PROXY) on the Dify host machine before running Docker Compose.

Comment out the proxy-related lines added in commit fix: fix proxy for docker #11681 in the Docker Compose configuration if the proxy settings are not needed.

These steps should help establish the connection successfully, similar to how it worked in version 0.13.2 [1].

I've tried both these suggestions but none of them work in 0.14.1, same issue.

crazywoola · 2024-12-19T10:34:25Z

#11681

I don't think it's related. Because these 2 settings have exist for a while.

Ynewtime · 2024-12-20T01:50:53Z

#11681

I don't think it's related. Because these 2 settings have exist for a while.

Not sure if it's related but as per the .env.example file comparison between 0.13.2 and 0.14.1, the HTTP(S)_PROXY config exist in 0.14.1 only?

AugNSo · 2024-12-20T02:01:09Z

@Ynewtime Hi, I am the one giving those 2 suggestions in #11739. If you comment out those 2 lines and then docker compose, the HTTP(S)_PROXY should no longer affect the container. You can look at the dify api container log for more detailed error tracing.

Ynewtime · 2024-12-20T03:34:29Z

@Ynewtime Hi, I am the one giving those 2 suggestions in #11739. If you comment out those 2 lines and then docker compose, the HTTP(S)_PROXY should no longer affect the container. You can look at the dify api container log for more detailed error tracing.

Hi there, thanks. I'ved tried (yesterday and today with the latest commit) commented out those 2 lines but same issue there. Kindly find the dify-api container full logs here:

2024-12-20 11:25:36 None of PyTorch, TensorFlow >= 2.0, or Flax have been found. Models won't be available and only tokenizers, configuration and file/data utilities can be used.
2024-12-20 11:25:30 Running migrations
2024-12-20 11:25:43 2024-12-20 03:25:43,435.435 INFO [MainThread] [utils.py:148] - Note: NumExpr detected 16 cores but "NUMEXPR_MAX_THREADS" not set, so enforcing safe limit of 8.
2024-12-20 11:25:43 2024-12-20 03:25:43,435.435 INFO [MainThread] [utils.py:160] - NumExpr defaulting to 8 threads.
2024-12-20 11:25:47 /app/api/.venv/lib/python3.12/site-packages/tencentcloud/hunyuan/v20230901/models.py:6034: SyntaxWarning: invalid escape sequence '\_'
2024-12-20 11:25:47   """function名称，只能包含a-z，A-Z，0-9，\_或-
2024-12-20 11:25:49 /app/api/.venv/lib/python3.12/site-packages/jieba/__init__.py:44: SyntaxWarning: invalid escape sequence '\.'
2024-12-20 11:25:49   re_han_default = re.compile("([\u4E00-\u9FD5a-zA-Z0-9+#&\._%\-]+)", re.U)
2024-12-20 11:25:49 /app/api/.venv/lib/python3.12/site-packages/jieba/__init__.py:46: SyntaxWarning: invalid escape sequence '\s'
2024-12-20 11:25:49   re_skip_default = re.compile("(\r\n|\s)", re.U)
2024-12-20 11:25:49 /app/api/.venv/lib/python3.12/site-packages/jieba/finalseg/__init__.py:78: SyntaxWarning: invalid escape sequence '\.'
2024-12-20 11:25:49   re_skip = re.compile("([a-zA-Z0-9]+(?:\.\d+)?%?)")
2024-12-20 11:25:49 /app/api/.venv/lib/python3.12/site-packages/jieba/posseg/__init__.py:16: SyntaxWarning: invalid escape sequence '\.'
2024-12-20 11:25:49   re_skip_detail = re.compile("([\.0-9]+|[a-zA-Z0-9]+)")
2024-12-20 11:25:49 /app/api/.venv/lib/python3.12/site-packages/jieba/posseg/__init__.py:17: SyntaxWarning: invalid escape sequence '\.'
2024-12-20 11:25:49   re_han_internal = re.compile("([\u4E00-\u9FD5a-zA-Z0-9+#&\._]+)")
2024-12-20 11:25:49 /app/api/.venv/lib/python3.12/site-packages/jieba/posseg/__init__.py:18: SyntaxWarning: invalid escape sequence '\s'
2024-12-20 11:25:49   re_skip_internal = re.compile("(\r\n|\s)")
2024-12-20 11:25:49 /app/api/.venv/lib/python3.12/site-packages/jieba/posseg/__init__.py:21: SyntaxWarning: invalid escape sequence '\.'
2024-12-20 11:25:49   re_num = re.compile("[\.0-9]+")
2024-12-20 11:25:58 Preparing database migration...
2024-12-20 11:25:59 2024-12-20 03:25:59,232.232 INFO [pre_load_builtin_providers_cache] [font_manager.py:1578] - generated new fontManager
2024-12-20 11:26:04 Database migration skipped
2024-12-20 11:26:07 [2024-12-20 03:26:07 +0000] [1] [INFO] Starting gunicorn 23.0.0
2024-12-20 11:26:07 [2024-12-20 03:26:07 +0000] [1] [INFO] Listening at: http://0.0.0.0:5001 (1)
2024-12-20 11:26:07 [2024-12-20 03:26:07 +0000] [1] [INFO] Using worker: gevent
2024-12-20 11:26:07 [2024-12-20 03:26:07 +0000] [52] [INFO] Booting worker with pid: 52
2024-12-20 11:26:09 None of PyTorch, TensorFlow >= 2.0, or Flax have been found. Models won't be available and only tokenizers, configuration and file/data utilities can be used.
2024-12-20 11:26:12 2024-12-20 03:26:12,027.027 INFO [MainThread] [utils.py:148] - Note: NumExpr detected 16 cores but "NUMEXPR_MAX_THREADS" not set, so enforcing safe limit of 8.
2024-12-20 11:26:12 2024-12-20 03:26:12,027.027 INFO [MainThread] [utils.py:160] - NumExpr defaulting to 8 threads.
2024-12-20 11:26:27 2024-12-20 03:26:27,092.092 WARNING [Dummy-1] [version.py:37] - Check update version error: HTTPSConnectionPool(host='updates.dify.ai', port=443): Max retries exceeded with url: /?current_version=0.14.1 (Caused by ProxyError('Unable to connect to proxy', NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f64e2e2d9d0>: Failed to establish a new connection: [Errno 111] Connection refused'))).
2024-12-20 11:27:13 2024-12-20 03:27:13,899.899 INFO [Dummy-2] [_base_client.py:1086] - Retrying request to /chat/completions in 0.470940 seconds

My WSL2 configuration (.wslconfig):

# https://learn.microsoft.com/en-us/windows/wsl/wsl-config#main-wsl-settings
[wsl2]
networkingMode=mirrored
dnsTunneling=true
autoProxy=true

# https://learn.microsoft.com/en-us/windows/wsl/wsl-config#experimental-settings
[experimental]
autoMemoryReclaim=dropcache
sparseVhd=true
bestEffortDnsParsing=true
hostAddressLoopback=true

...notice that I've enabled the networkingMode=mirrored mode, which ensures the best network experience when developing in WSL2. With clash proxy enabled on Windows, you can use the clash proxy with no extra steps right in WSL2:

➜  docker git:(main) echo $http_proxy 
http://127.0.0.1:7890

But still, as I've mentioned, all the environment and configurations are the same for 0.13.2 and 0.14.1, but connection fails for 0.14.1 when configuring new Model Providers.

AugNSo · 2024-12-20T05:18:07Z

The log shows that your dify is still using the proxy setting.
2024-12-20 11:26:27 2024-12-20 03:26:27,092.092 WARNING [Dummy-1] [version.py:37] - Check update version error: HTTPSConnectionPool(host='updates.dify.ai', port=443): Max retries exceeded with url: /?current_version=0.14.1 (Caused by ProxyError('Unable to connect to proxy', NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f64e2e2d9d0>: Failed to establish a new connection: [Errno 111] Connection refused'))).

Make sure you unset the HTTP_PROXY and HTTPS_PROXY, all upper case.
You can also try the following:

Stop clash as system proxy and use clash's TUN mode instead.

yihong0618 · 2024-12-20T05:56:22Z

do we need to consider remove the http_proxy and https_proxy in env args...it will break some users

AugNSo · 2024-12-20T06:03:44Z

#11681

I don't think it's related. Because these 2 settings have exist for a while.

@crazywoola This commit is added just 4 days ago, and is about the same time as Dify v0.14.0 rolled out when people start to upgrade and report issue.

By my understanding, this commit is trying to use proxy to pull docker image which I am sure there are other methods achieving the same. But not to digress from the discussion, the environment variables is passed to the dify api container as well. In the case of a proxy like 127.0.0.1:7890, dify will access its internal network address rather than the host machine, which caused problems.

Ynewtime · 2024-12-20T06:53:23Z

The log shows that your dify is still using the proxy setting. 2024-12-20 11:26:27 2024-12-20 03:26:27,092.092 WARNING [Dummy-1] [version.py:37] - Check update version error: HTTPSConnectionPool(host='updates.dify.ai', port=443): Max retries exceeded with url: /?current_version=0.14.1 (Caused by ProxyError('Unable to connect to proxy', NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f64e2e2d9d0>: Failed to establish a new connection: [Errno 111] Connection refused'))).

Make sure you unset the HTTP_PROXY and HTTPS_PROXY, all upper case. You can also try the following:
* Stop clash as system proxy and use clash's TUN mode instead.

"Make sure you unset the HTTP_PROXY and HTTPS_PROXY, all upper case" ---- this make no sense:

I've tried unsetting the HTTP(S)_PROXY for 0.14.1, unfortunately it doesn't work, same connection error.
Remember the 0.13.2 and 0.14.1 were started from the same environment with proxy on, but 0.13.2 works and 0.14.1 fails.
Unsetting the HTTP(S)_PROXY will also affect 0.13.2.

Stop clash as system proxy and use clash's TUN mode instead ---- this is not required because as I mentioned in the last comment:

I've enabled the networkingMode=mirrored mode, which ensures the best network experience when developing in WSL2. With clash proxy enabled on Windows, you can use the clash proxy with no extra steps right in WSL2

...which means as long as I enabled Clash as system proxy, WSL2 will have proxy support transparently, no need to manully config anything else in WSL2. And only with the proxy on, I will be able to connect to OpenAI and Claude endpoint from my WSL2 environment:

➜  docker git:(main) wget -q --spider https://claude.ai && echo "connected" || echo "not connected"
connected

AugNSo · 2024-12-20T07:28:00Z

I assume your actions are as follows: after you unset HTTP_PROXY and HTTPS_PROXY in WSL, run docker compose up -d again, the dify containers have been recreated, but the problem persists. If that's the case, I cannot replicate your problem, although I still suspect it is proxy related.
I don't quite understand your second and third points, but fix: fix proxy for docker #11681 is not present in 0.13.2.
Because with networkingMode=mirrored and autoProxy=true, WSL will automatically set the HTTP(S)_PROXY environment variable for you if you use clash as a system proxy. TUN mode achieves the same proxy function without triggering the above. I'm not suggesting that you not use a proxy. (You can set HTTP_PROXY and HTTPS_PROXY back once dify is up anyway if you want to stick with system proxy mode.)

I hope your problem gets resolved soon.

crazywoola · 2024-12-20T09:52:12Z

@AugNSo You are right, needs to be reverted.

yihong0618 · 2024-12-20T09:53:34Z

I assume your actions are as follows: after you unset HTTP_PROXY and HTTPS_PROXY in WSL, run docker compose up -d again, the dify containers have been recreated but the problem persists. If that's the case, I cannot replicate your problem though I still suspect its proxy related.

I don't quite get your second and third point, but fix: fix proxy for docker #11681 is not present in 0.13.2.

Because with networkingMode=mirrored and autoProxy=true, WSL will automatically set the HTTP(S)_PROXY environment for you if you use clash as system proxy. TUN mode achieves the same proxy function without triggering the above… I'm not suggesting you not to use proxy. (You can set HTTP_PROXY and HTTPS_PROXY back once the container is up)

Hope your problem get resolved soon.

nice explain!

yihong0618 · 2024-12-20T09:55:02Z

It's true that living in mainland China comes with a lot of internet knowledge.........

gaoyuexit · 2024-12-23T09:24:30Z

I have the same question.

AugNSo · 2024-12-23T10:13:40Z

@gaoyuexit the latest code has already fixed the issue.

gaoyuexit · 2024-12-23T10:41:26Z

@gaoyuexit the latest code has already fixed the issue.

I am using the latest code, maybe it's my own problem?
Is there any documentation for using Clash proxy?

Ynewtime · 2024-12-25T03:22:11Z

It works now.

With the #11906 fix, now 0.14.1 can connect to OpenAI endpoint, same as 0.13.2 (in China Mainland, enable WSL2 mirrored networkingMode and Clash proxy).

Kudos to the team!

dosubot bot added the 🐞 bug Something isn't working label Dec 19, 2024

crazywoola mentioned this issue Dec 20, 2024

revert: these 2 settings #11906

Merged

5 tasks

laipz8200 closed this as completed in #11906 Dec 20, 2024

crazywoola mentioned this issue Dec 23, 2024

SSL error without proxy on self hosted dify #11963

Closed

5 tasks

dosubot bot mentioned this issue Jan 16, 2025

I found an abnormal bug while using HTTP to request nodes #12792

Open

5 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

'Connection Error' when setup OpenAI on Model Provider after upgrading to 0.14.1 #11839

'Connection Error' when setup OpenAI on Model Provider after upgrading to 0.14.1 #11839

Ynewtime commented Dec 19, 2024 •

edited

Loading

dosubot bot commented Dec 19, 2024

Ynewtime commented Dec 19, 2024

crazywoola commented Dec 19, 2024

Ynewtime commented Dec 20, 2024

AugNSo commented Dec 20, 2024

Ynewtime commented Dec 20, 2024 •

edited

Loading

AugNSo commented Dec 20, 2024 •

edited

Loading

yihong0618 commented Dec 20, 2024

AugNSo commented Dec 20, 2024 •

edited

Loading

Ynewtime commented Dec 20, 2024

AugNSo commented Dec 20, 2024 •

edited

Loading

crazywoola commented Dec 20, 2024

yihong0618 commented Dec 20, 2024

yihong0618 commented Dec 20, 2024

gaoyuexit commented Dec 23, 2024

AugNSo commented Dec 23, 2024

gaoyuexit commented Dec 23, 2024

Ynewtime commented Dec 25, 2024

'Connection Error' when setup OpenAI on Model Provider after upgrading to 0.14.1 #11839

'Connection Error' when setup OpenAI on Model Provider after upgrading to 0.14.1 #11839

Comments

Ynewtime commented Dec 19, 2024 • edited Loading

Self Checks

Dify version

Cloud or Self Hosted

Steps to reproduce

✔️ Expected Behavior

❌ Actual Behavior

dosubot bot commented Dec 19, 2024

Ynewtime commented Dec 19, 2024

crazywoola commented Dec 19, 2024

Ynewtime commented Dec 20, 2024

AugNSo commented Dec 20, 2024

Ynewtime commented Dec 20, 2024 • edited Loading

AugNSo commented Dec 20, 2024 • edited Loading

yihong0618 commented Dec 20, 2024

AugNSo commented Dec 20, 2024 • edited Loading

Ynewtime commented Dec 20, 2024

AugNSo commented Dec 20, 2024 • edited Loading

crazywoola commented Dec 20, 2024

yihong0618 commented Dec 20, 2024

yihong0618 commented Dec 20, 2024

gaoyuexit commented Dec 23, 2024

AugNSo commented Dec 23, 2024

gaoyuexit commented Dec 23, 2024

Ynewtime commented Dec 25, 2024

Ynewtime commented Dec 19, 2024 •

edited

Loading

Ynewtime commented Dec 20, 2024 •

edited

Loading

AugNSo commented Dec 20, 2024 •

edited

Loading

AugNSo commented Dec 20, 2024 •

edited

Loading

AugNSo commented Dec 20, 2024 •

edited

Loading