-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[error]: /turing/conversation/create: failed to parse response body #370
Comments
Hi, yes it seems Bing has updated something on their end but I have a solution for you. Update the project to latest on main branch, I also posted this here: waylaidwanderer/node-chatgpt-api#378 (comment) and updated the project accordingly here #369 You will need to set BINGAI_TOKEN in your ./api/.env file (or in your browser if using "user_provided") to your full cookies string from bing.com, instead of just the This is confirmed working for me Using firefox and dev tools, i get my cookies string from here:You can use any browser, just fish around in the network tab to see which request has a Cookie value in the Request headersThanks for checking out the project, I'm glad you're enjoying it! |
@feng2505664393 let me know if the above worked for you There were also some other suggestions at the bottom of this issues page waylaidwanderer/node-chatgpt-api#378 |
Sorry, sir. I used an old version of chat-clone. In order to try the solution you provided, I had to update my Docker image. It took me some time, but the exciting thing is that I just finished all the work on the solution and it works! |
Awesome, glad to help! |
if like me you do not like manual steps to derive BING_API_TOKEN configuration, this can be automated
python selenium function to get BING_API_TOKEN
|
hello, guys. this project is really fantastic, i have been using it for a while time. but,yesterday,when i asked bingAI,it returned a error. Have you ever see this error?
An error occurred. Please try again in a few moments. Error message: /turing/conversation/create: failed to parse response body.
...
response body is a html. i put it into chrome. the follow is something which chrome show.
The text was updated successfully, but these errors were encountered: