-
Notifications
You must be signed in to change notification settings - Fork 443
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] Token Regeneration Error/Login Errors #71
Comments
It's up again |
no!!! It seems to have gone down again |
Has it been solved?I still can't log in |
It seems to have gone down again |
I can login in the browser
|
seems like an api only error |
Looking forward to a good solution to check if the error was raised by the official server. |
Is there any fix yet? |
i believe this error is internal to library now since i am able to use other wrappers :-) |
well, what do I do then? I am new to it and I don't have access to the site |
This was a server error and it has since been fixed |
I still get the same error, that in #80 |
If you are in China, you must use proxy: bupticybee/ChineseAiDungeonChatGPT#23 |
I am not in China, but I'll try |
It does not work with proxy as well |
I'm unsure how to debug the auth in this repo but if you use https://github.com/acheong08/ChatGPT with |
I'll try |
This is the firs time I'm seeing this. Looks like OpenAI added an additional check that's preventing the TLS approach from working at the moment: CleanShot.2022-12-11.at.15.26.12.mp4 |
They put Cloudflare in front of their site as a CDN, which makes a lot of sense, but it now means they have Cloudflare's additional security checks against bots. There seems to be a repo project for bypassing this: https://github.com/VeNoMouS/cloudscraper I wish they would just release an API, I'd gladly pay to use it. :/ |
ChatGPT is using version 2 Captcha challenge of Cloudflare. I don't think this is possible using VeNoMouS/cloudscraper |
Also having problems.
|
I'm seeing a lot of people report issues within the token regeneration process, If you're affected, please react.
The text was updated successfully, but these errors were encountered: