-
Notifications
You must be signed in to change notification settings - Fork 780
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
not working #627
Comments
Yeah.. same here +1 |
+1 :( |
+1 |
Same issue: chatGPTbox version 2.4.9, Firefox 122.0.1, Apple Macbook Pro M1 Pro The requests are actually getting created on the chatGPT Web UI, because if you remove the flag from the |
Same here! |
Looks like OpenAI has put a restriction on this maybe. Mine's also waiting on a response to no avail. |
+1 :( |
+1^3 |
Over a week and no response from the developers, it would be a huge damn shame if this project was abandoned... |
You can temporarily use alternatives such as Claude, Bing, API Key Mode, etc. I may not have much time to deal with this issue in the near future. If I have time, I will try to push a temporary version to fix this issue. |
The same issue - WIn10 Firefox 123.0 - can you make box for username and password to solve it Bing - Claude - API Key Mode - |
These are different errors from the one in this issue.
I get the same error but it might be because I'm using Firefox?
Which country are you from? Claude is available only in these regions https://www.anthropic.com/claude-ai-locations
Do you have a paid account? API Mode is not available for OpenAI free accounts. |
It seems things have returned to normal lately. How are things going over there? It looks like OpenAI is adjusting their verification strategy frequently. Edit: Currently, it seems that some people can use it while some still cannot. I want to know if you still cannot use it. |
No, I cannot use it still. It does the same thing by not loading a response |
+1 |
Hey, its dosent work ;( The problem sind weeks... |
fixed in 1fc3cd8 After conducting some investigation, I found that OpenAI seems to have adopted different strategies for different accounts. Since my account still adheres to the traditional SSE strategy, I mistakenly assumed that everything was still normal. I have now adapted to the new WebSocket strategy and automatically adopted the appropriate strategy according to OpenAI's response. |
Yesss thank you!! |
Thank you! You are the man! ❤️👍 |
@gitdine Please provide a screenshot of Network section. It seems that the request was not successfully sent from the beginning |
@gitdine please close chatgpt website and try again, there should be something in the network tab |
@gitdine and then open the chatgpt website, press F12 and send a message again, take a console screenshot |
For some reason after doing this, the extension has started responding to my messages again... |
@gitdine Are you always able to receive responses now? You can also try restarting your browser. Overall, based on the information you provided earlier, it seems that the message was simply not successfully sent. I'm not sure if this is due to a network problem. |
My bad, thanks for catching that. It seems that if I open the ChatGPT website and send a message that way first, then the extension will work normally afterward, otherwise it gets stuck on 'Waiting for response...' |
@gitdine Indeed, there are some accounts that must be handled in this way in order for the extension to respond normally. I'm not sure if it's because of OpenAI's policy, but for me, my account can respond in the background without needing to keep the ChatGPT website open. |
@josStorer |
Thank you @josStorer. May God bless you. Your program is very beautiful and useful. Thank you for your hard work, patience and dedication. Thank you for your time and effort in solving the previous issue. We appreciate the time you took. I want to give you a gift as a thank you. If you can message me your contact. |
Hey @josStorer Version I have your new version, but the summary doesn't work. It doesn't want to work, no error message like back then. It just doesn't matter. |
Its not responding when given a prompt. When you click the refresh or retry/regenerate button it says:
Error:
{
"detail": {
"message": "Conversation key not found. Try starting a new conversation."
}
}
The text was updated successfully, but these errors were encountered: