Wenjie Fu

> from you screenshot it seems to the cors issue with your openai api provider? but if i forward the api provider ip&port to local, then the nextweb works well,...

sorry, close the issue by accident.

> from you screenshot it seems to the cors issue with your openai api provider? Besides, I can access the API service well via curl command: ``` curl --location 'http://ip:port/v1/chat/completions'...

I have used Burp Suite to capture http package, and the result demonstrate that when using a API deployed in localhost, the request packages are sent correctly: ``` OPTIONS /v1/chat/completions...

> 你是不是使用了 NAT 进行了端口映射，这可能会有 NAT 环回的问题。 我应该没有主动配置 NAT 端口映射，而且 NAT 环回会导致 NextChat这类 app不能 send url request 吗？主要用 curl又是好的，就很奇怪。

> > Same problem, Macos + Docker, Set api to localhost works fine, but it won't work if set to my own server ip, but I can access the api...

@fred-bf I believe the bug tag should be added back, since another issue #2810 reveals this bug too. This bug seems to exist for a period.

> I don't have any issues with this; it has been running on Kubernetes (k8s) without problems Are you using an Mac client? It seems that the issue only exist...

> I just tried build a development macOS client, it could make request to custom ip. But when switching to a online version, I could reproduce this issue. It might...

@fred-bf Hi, you are absolutely right! i check the console log, and find the mixed content error:  So, this issue on web version can be solved by allowing the...