-
Notifications
You must be signed in to change notification settings - Fork 923
Exception: Authentication failed #46
Comments
It means you don't have beta access |
In fact, I have new bing chat access |
The same issue, I have beta access but still get "Authentication failed". |
A tip from the Very Large Lettered status quo: Now, how long have you waited for that beta access, guys? Any tips to expedite that before they chroot jail it further? |
How did you write the cookies.json. Is the format correct? Does it include the _U cookie? What version did you run? Did you point it to the right path? |
My [
{
"domain": "www.bing.com",
"hostOnly": true,
"httpOnly": false,
"name": "_U",
"path": "/",
"sameSite": null,
"secure": false,
"session": true,
"storeId": null,
"value": "..."
}
] |
I'll add more documentation for developer usage |
Set |
Does |
And the issue here is that you didn't set the cookie path as environment variable |
^ This is the solution |
Found the issue. You might want to check it |
Closing and moving over to the other issue |
ReOpening |
We got new info that people with the KievRPSSecAuth cookie cannot use the program for some reason. |
Oh wait there was bug in release |
And send the error logs |
Can you show the bit before that? |
It shows the error code and response text |
Thanks I will look into this |
This may be caused by a banned region, such as China. This can be solved by adding this to the header。Or use proxy. |
Exactly. People can use extensions in browser such as ModHeader to set |
|
Will do. Thanks for the fix |
I've made a cookies.json, but still error like this picture
The text was updated successfully, but these errors were encountered: