Skip to content
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

Success: null #470

Open
WaterHyacinthInNANHU opened this issue Sep 11, 2023 · 7 comments · Fixed by danny-avila/nodejs-gpt#7 · May be fixed by #481
Open

Success: null #470

WaterHyacinthInNANHU opened this issue Sep 11, 2023 · 7 comments · Fixed by danny-avila/nodejs-gpt#7 · May be fixed by #481
Labels
bug Something isn't working

Comments

@WaterHyacinthInNANHU
Copy link

Describe the bug
I'm using BingAIClient. After several successful queries, the API server returns error code 503 with the error message: {"error":"null"}. Please help~

Screenshots
image

Node.js version (please complete the following information):

  • OS: Linux 4090 5.15.0-82-generic 20.04.1-Ubuntu
  • Node v20.5.1

Package version (please complete the following information):

@WaterHyacinthInNANHU WaterHyacinthInNANHU added the bug Something isn't working label Sep 11, 2023
@vaibhavard
Copy link

vaibhavard commented Sep 14, 2023

Same Issue from the past 5 days. BingAI No longer works properly.

Sometimes the issue disappears but mostly it shows error:null
image

@jegue
Copy link

jegue commented Sep 14, 2023

yeah same here! If using the SRCHLANG cookie.

@vaibhavard
Copy link

I use _U cookie .. Whats srchlang cookie?

@Richard-Weiss
Copy link
Contributor

@WaterHyacinthInNANHU
It seems to be a problem on Microsoft's side. Sometimes a conversationSignature won't be returned when sending the conversation POST.
I don't experience the problem anymore after getting new optionSets and SliceIds from a vanilla request, however there still seems to be some problems on Microsoft's side, mainly InternalServiceErrors for normal POST requests.
So you might just see the error "Error processing request." displayed sometimes.
The issue isn't really related to the repo code itself, but we should leave it open until the errors disappear, so nobody creates a new issue.

@WaterHyacinthInNANHU
Copy link
Author

@WaterHyacinthInNANHU It seems to be a problem on Microsoft's side. Sometimes a conversationSignature won't be returned when sending the conversation POST. I don't experience the problem anymore after getting new optionSets and SliceIds from a vanilla request, however there still seems to be some problems on Microsoft's side, mainly InternalServiceErrors for normal POST requests. So you might just see the error "Error processing request." displayed sometimes. The issue isn't really related to the repo code itself, but we should leave it open until the errors disappear, so nobody creates a new issue.

It is true that starting a new conversation solves this. Thanks for your timely help!

@Richard-Weiss
Copy link
Contributor

Richard-Weiss commented Sep 17, 2023

Yeah, it seems to have "solved itself" i.e. they fixed it on their end.
--Edit--
You'll still get the issue occasionally if you are not using the encrypted request and websocket.
So it's probably best to see #481 for a real fix.

@michael-ts
Copy link

I am getting this error out of the gate. I have not been able to get any successful responses, ever.
One thing that is different than the above error is that once I paste my cookies into settings.txt the error message changes from "|BingProdUnAuthenticatedUsers|" to "|BingProd|".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
5 participants