search

xqdoo00o / ChatGPT-to-API

Scalable unofficial ChatGPT API for production.
648 stars 129 forks source link

unable to check chat requirement #64

Closed lianguooo closed 2 months ago

lianguooo commented 2 months ago

post: /v1/chat/completions data: { "model": "gpt-3.5-turbo", "messages": [ { "role": "system", "content": "You are a helpful assistant." }, { "role": "user", "content": "Hello!" } ] } response: {"error":"unable to check chat requirement"}

但是请求模型正常 get: /v1/models response: { "data": [ { "created": 1688888888, "id": "gpt-3.5-turbo", "object": "model", "owned_by": "chatgpt-to-api" }, { "created": 1688888888, "id": "gpt-4", "object": "model", "owned_by": "chatgpt-to-api" } ], "object": "list" }

xqdoo00o commented 2 months ago

参考之前issue

xqdoo00o commented 2 months ago

ip呢，是否可用浏览器正常登录使用。。profile设置错了，是代码里那个map里左侧的键名，不是值名

lianguooo commented 2 months ago

IP 是可用的，profile设置为chrome_125也是同样的问题，是不是125版本太高了。

maxduke commented 2 months ago

IP 是可用的，profile设置为chrome_125也是同样的问题，是不是125版本太高了。

键值哪里有125的版本。。。？ 还有ua不要双引号

lianguooo commented 2 months ago

IP 是可用的，profile设置为chrome_125也是同样的问题，是不是125版本太高了。

键值哪里有125的版本。。。？ 还有ua不要双引号

您好，我现更新为firefox_123了，但仍无法使用。UA不加双引号会无法启用，因为包含空格了，麻烦了

maxduke commented 2 months ago

IP 是可用的，profile设置为chrome_125也是同样的问题，是不是125版本太高了。

键值哪里有125的版本。。。？ 还有ua不要双引号

您好，我现更新为firefox_123了，但仍无法使用。UA不加双引号会无法启用，因为包含空格了，麻烦了

哦，你是直接export，不是docker-compose.yml。你直接官网不出盾？你服务器ipv4 ipv6都有？

lianguooo commented 2 months ago

哦，你是直接export，不是docker-compose.yml。你直接官网不出盾？你服务器ipv4 ipv6都有？ 直接访问官网会有人机验证，但是勾选后可进入网站，是这个原因造成的吗？

maxduke commented 2 months ago

对，那就是出盾了。要干净点的ip才行

On Wed, Jun 12, 2024 at 08:39 lianguooo @.***> wrote:

哦，你是直接export，不是docker-compose.yml。你直接官网不出盾？你服务器ipv4 ipv6都有？ 直接访问官网会有人机验证，但是勾选后可进入网站，是这个原因造成的吗？

— Reply to this email directly, view it on GitHub https://github.com/xqdoo00o/ChatGPT-to-API/issues/64#issuecomment-2161849867, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADLUBHNGXBAA2RQKF2B7W3ZG6KC5AVCNFSM6AAAAABJCROIY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRRHA2DSOBWG4 . You are receiving this because you commented.Message ID: @.***>

bi1101 commented 2 months ago

Hi sir, I have added environment variables as follows in docker but the issue persists.

The Ip is from my PC and I can access chatgpt.com normally, no CAPTCHA required. I also noticed on the official websites, the chat requirement sometimes return 403 error codes but the UI seems to auto retry until it gets 200, could this be the reason for this error?

CLIENT_PROFILE = chrome_124 UA = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36 Edg/125.0.0.0

maxduke commented 2 months ago

Currently, the official requirements endpoint has a timeout problem.

On Wed, Jun 12, 2024 at 20:13 bi1101 @.***> wrote:

Hi sir, I have added environment variables as follows in docker but the issue persists.

The Ip is from my PC and I can access chatgpt.com normally, no CAPTCHA required. I also noticed on the official websites, the chat requirement sometimes return 403 error codes but the UI seems to auto retry until it gets 200, could this be the reason for this error?

CLIENT_PROFILE = chrome_124 UA = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36 Edg/125.0.0.0

— Reply to this email directly, view it on GitHub https://github.com/xqdoo00o/ChatGPT-to-API/issues/64#issuecomment-2162856763, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADLUBDWDUIWBS43I7ZD66TZHA3PZAVCNFSM6AAAAABJCROIY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRSHA2TMNZWGM . You are receiving this because you commented.Message ID: @.***>

bi1101 commented 2 months ago

Currently, the official requirements endpoint has a timeout problem.

Can we do something about it?

maxduke commented 2 months ago

Wait 🤷‍♂️

On Wed, Jun 12, 2024 at 21:13 bi1101 @.***> wrote:

Currently, the official requirements endpoint has a timeout problem.

Can we do something about it?

— Reply to this email directly, view it on GitHub https://github.com/xqdoo00o/ChatGPT-to-API/issues/64#issuecomment-2162979186, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADLUBDZ45SF23G3Y5BG6ETZHBCQJAVCNFSM6AAAAABJCROIY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRSHE3TSMJYGY . You are receiving this because you commented.Message ID: @.***>

bi1101 commented 2 months ago

In the meantime, to over come this issue, I found that if we do not use the account.txt, access_tokens.json & cookies.json, the problem is solved. The only drawback is we can't use GPT 4.

maxduke commented 2 months ago

This is because no account mode uses another endpoint for chat requirements

On Wed, Jun 12, 2024 at 23:00 bi1101 @.***> wrote:

In the meantime, to over come this issue, I found that if we do not use the account.txt, access_tokens.json & cookies.json, the problem is solved. The only drawback is we can't use GPT 4.

— Reply to this email directly, view it on GitHub https://github.com/xqdoo00o/ChatGPT-to-API/issues/64#issuecomment-2163265213, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADLUBFSIEID4ZGZPBS24X3ZHBPAXAVCNFSM6AAAAABJCROIY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRTGI3DKMRRGM . You are receiving this because you commented.Message ID: @.***>