Exception: Authentication failed about edgegpt HOT 34 CLOSED

It means you don't have beta access

from edgegpt.

In fact, I have new bing chat access

from edgegpt.

The same issue, I have beta access but still get "Authentication failed".

from edgegpt.

A tip from the Very Large Lettered status quo:
UPDATE 2023/02/14 - Do not use for now while I verify its safety

Now, how long have you waited for that beta access, guys? Any tips to expedite that before they chroot jail it further?

from edgegpt.

In fact, I have new bing chat access

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?

from edgegpt.

from edgegpt.

My cookie.json:

[
    {
        "domain": "www.bing.com",
        "hostOnly": true,
        "httpOnly": false,
        "name": "_U",
        "path": "/",
        "sameSite": null,
        "secure": false,
        "session": true,
        "storeId": null,
        "value": "..."
    }
]

from edgegpt.

I've made a cookies.json, but still error like this picture

I see. You didn't set the environment variable

from edgegpt.

I'll add more documentation for developer usage

from edgegpt.

Set export COOKIE_FILE=/path/to/cookies.json

from edgegpt.

My cookie.json:

[
    {
        "domain": "www.bing.com",
        "hostOnly": true,
        "httpOnly": false,
        "name": "_U",
        "path": "/",
        "sameSite": null,
        "secure": false,
        "session": true,
        "storeId": null,
        "value": "..."
    }
]

The json that is copied with the extension in the description looks like this.

from edgegpt.

Does _U show up anywhere there?

from edgegpt.

And the issue here is that you didn't set the cookie path as environment variable

from edgegpt.

Set export COOKIE_FILE=/path/to/cookies.json

^ This is the solution

from edgegpt.

from edgegpt.

from edgegpt.

from edgegpt.

• #48

Found the issue. You might want to check it

from edgegpt.

Closing and moving over to the other issue

from edgegpt.

ReOpening

from edgegpt.

We got new info that people with the KievRPSSecAuth cookie cannot use the program for some reason.

from edgegpt.

from edgegpt.

Oh wait there was bug in release

from edgegpt.

Try https://github.com/acheong08/EdgeGPT/releases/tag/0.0.42

from edgegpt.

And send the error logs

from edgegpt.

from edgegpt.

Can you show the bit before that?

from edgegpt.

It shows the error code and response text

from edgegpt.

from edgegpt.

Thanks I will look into this

from edgegpt.

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.
"x-forwarded-for": "8.8.8.8" @acheong08

from edgegpt.

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. "x-forwarded-for": "8.8.8.8" @acheong08

Exactly. People can use extensions in browser such as ModHeader to set "x-forwarded-for": "8.8.8.8".
However we do not know how to set it in a python script.

from edgegpt.

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. "x-forwarded-for": "8.8.8.8" @acheong08

Exactly. People can use extensions in browser such as ModHeader to set "x-forwarded-for": "8.8.8.8". However we do not know how to set it in a python script.

you can edit this or wait for author update

from edgegpt.

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. "x-forwarded-for": "8.8.8.8" @acheong08

Will do. Thanks for the fix

from edgegpt.