Skip to content

[Bug]: Bing AI null error after giving cookie api key #1032

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

Closed
1 task done
Peteryhs opened this issue Oct 9, 2023 · 3 comments
Closed
1 task done

[Bug]: Bing AI null error after giving cookie api key #1032

Peteryhs opened this issue Oct 9, 2023 · 3 comments
Labels
🐛 bug Something isn't working

Comments

@Peteryhs
Copy link

Peteryhs commented Oct 9, 2023

What happened?

After inputing the full cookie string into the browser end, bing ai is returning "Something went wrong. Here's the specific error message we encountered: null".

I have also tried with modifying the bing ai key value in .env and the _U string.

However, none of them seems to work out.

System: Zorion OS 16.3 (Ubuntu)
Installation method: Docker

Steps to Reproduce

  1. Attempt to add an api key to the bing ai section
  2. Attempt to send a message

What browsers are you seeing the problem on?

Firefox

Relevant log output

No response

Screenshots

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@Peteryhs Peteryhs added the 🐛 bug Something isn't working label Oct 9, 2023
@Peteryhs Peteryhs changed the title [Bug]: Bing AI null error after giving cookie api key [Question]: Bing AI null error after giving cookie api key Oct 9, 2023
@Peteryhs Peteryhs changed the title [Question]: Bing AI null error after giving cookie api key [Bug]: Bing AI null error after giving cookie api key Oct 9, 2023
@danny-avila
Copy link
Owner

Closing in favor of #1028

There was an update to the Bing backend API. there is a fix, but not yet merged to the dependency we're using: waylaidwanderer/node-chatgpt-api#481

@danny-avila
Copy link
Owner

I will probably fork the dependency at this point or we may be waiting weeks

@danny-avila
Copy link
Owner

#1050 fix is officially merged

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
Development

No branches or pull requests

2 participants