This repository has been archived by the owner on Nov 18, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 35
giving error with newly created chatgpt account. it is working fine with the old one. can anyone explain the cause Thanks! #31
Comments
yeah i am having the same issue! |
is this fixed yet? |
no |
PR alreay pushed, wait approved, you can use it at https://github.com/Barrierml/reverse-engineered-chatgpt |
ty for fixing it bro i really need it, im waiting for it to get approved |
i am trying to run your fix, but it is showing same error, what am i doing wrong? i have downloaded your fork as zip and trying to run the syncchatgpt example |
# you can do like this
pip uninstall re-gpt
pip install git+https://github.com/Barrierml/reverse-engineered-chatgpt
|
i dont know why it didnt work earlier but it is working now |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
File "C:\Users\dell\Documents\python projects\rdpapi\chatgpt\gpt.py", line 15, in
for message in conversation.chat(prompt):
File "C:\Users\dell\AppData\Local\Programs\Python\Python312\Lib\site-packages\re_gpt\sync_chatgpt.py", line 135, in chat
raise UnexpectedResponseError(error, server_response)
re_gpt.errors.UnexpectedResponseError: An unexpected error occurred. Error message: 'NoneType' object is not subscriptable.
This is what the server returned: {"wss_url":"wss://chatgpt-async-webps-prod-southcentralus-5.webpubsub.azure.com/client/hubs/conversations?access_token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJodHRwczovL2NoYXRncHQtYXN5bmMtd2VicHMtcHJvZC1zb3V0aGNlbnRyYWx1cy01LndlYnB1YnN1Yi5hS3JmaEl2YXlqekhlNCIsInJvbGUiOlsid2VicHVic3ViLmpvaW5MZWF2ZUdyb3VwLnVzZXIteXU2M3cxTVNvbGFLcmZoSXZheWp6SGU0Il0sIndlYnB1YnN1Yi5ncm91cCI6WyJ1c2VyLXl1NjN3MU1Tb2xhS3JmaEl2YXlqekhlNCJdfQ.U-mcH6ZxMlj_vEKWUgOyKK89isQGVZP4ueWmWht7EA0","expires_at":"2024-03-02T21:55:23.950182+00:00","conversation_id":"f82ec126-2e71-4183-ab3e-607dbeb6501c","response_id":"85e449926c9fde5b-MCT","websocket_request_id":null}.
The text was updated successfully, but these errors were encountered: