-
Notifications
You must be signed in to change notification settings - Fork 446
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
[BUG] got 403 with openai needs to review the security
#112
Comments
Just found that the same process is required on the web page. |
Same issue, just started ~30 mins ago. Happens with or without VPN. I cannot refresh my token through the client, fails on Step 1, but if I fetch a token manually from the website I can get this response:
|
It's to do with and their (new) cloudflare hCaptcha implementation. Once you pass the security check, the browser stores a |
Here's some more info on their cookies: There is a _cf_bm cookie that is specifically to prevent bots. I wish openAI would just add an option to pay for an API so we could just stop the arms race. :D |
I couldn't beat the CF challenge but this fork allows you to pass the required cookies and user-agent as Options: https://github.com/sawyer/PyChatGPT |
Tracking here: acheong08/ChatGPT#261 cf_clearance cookie supported |
I had the same problem |
Your fork doesn't seem to work for me. Part 3 of auth flow fails with HTTP 400 Cloudflare error. I've only added the extra 3 parameters to |
Email/Password authentication no longer supported. Using session tokens now |
I've tried that as well, but it wasn't successful either, maybe I'm not initializing correctly (email/password is not an optional parameter in Auth).
I've captured the last XHR call in the browser, then used the Cookies in the response. Access token is from When I first try to ask something from the bot I get HTTP 401 "Could not parse your authentication token. Please try signing in again.". Wish we could just have an official API instead of relying on hacks :( |
@nistvan86 This hasn't been fixed by here yet. You can check out https://github.com/acheong08/ChatGPT/blob/cloudflare/wiki/Setup.md while you wait |
Me too. I hate maintaining the hacks when they actively try to sabotage us |
Yeah, but I was trying the fork of @sawyer which supposed to work with the extra cf attributes.
I don't blame them though. This thing is a money sink to operate. |
The main branch doesn't https://github.com/acheong08/ChatGPT/blob/main/wiki/Setup.md which is https://github.com/acheong08/ChatGPT/releases/tag/0.0.38.8
Same here. I would pay extravagant prices for their services, even if it's not an API. |
Two possible reasons:
|
CF is killing all bots.. |
Yes. Theres. |
Already bypassed the new CF update. Just need to wait a bit more. Join the discussion: |
still 1.0.8 in change log, not rleased yet? |
Describe the bug
When using pychatgpt normally, a 403 status code is returned with an html page requesting verification of connection security. And then asking any questions will return this. Restarting pychatgpt will not fix the problem, nor will the token be deemed invalid and reacquired.
To Reproduce
Steps to reproduce the behavior:
pip install chatgptpy --upgrade
Options()
chat.ask(prompt)
Expected behavior
The program can handle the problem or report an error.
Screenshots
If applicable, add screenshots to help explain your problem.
Version Info (please complete the following information):
Additional context
options
Provide information on each section, or your issue will be closed.
The text was updated successfully, but these errors were encountered: