-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Bug: Twitter Authentication fails on Cloud. Error 399 #2225
Comments
Hello @yongkangc! Welcome to the elizaOS community. Thank you for opening your first issue; we appreciate your contribution. You are now an elizaOS contributor! |
Twitter saw that you are into a Google sever and probably enforced a block because of that.
…On Mon, Jan 13, 2025 at 08:46, YK ***@***.***(mailto:On Mon, Jan 13, 2025 at 08:46, YK <<a href=)> wrote:
Describe the bug
I am trying to deploy eliza on [gce](https://cloud.google.com/products/compute?hl=en), however i am getting error on authentication error 399 when logging in causing the login to fail.
{
"errors"
: [{
"code"
:
399
,
"message"
:
"
Incorrect. Please try again. g;173669734519940919:-1736697345244:ILSZ2qNWESdWgKjC1KLSxaWZ:8
"
}]
}
To Reproduce
Expected behavior
Screenshots
[image.png (view on web)](https://github.com/user-attachments/assets/d932d52d-a618-4494-9b4c-2cc0e2fc2920)
Additional context
—
Reply to this email directly, [view it on GitHub](#2225), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BE5QO4HWT2TR6WSJYGI2QYL2KMLF7AVCNFSM6AAAAABVBTQAMCVHI2DSMVQWIX3LMV43ASLTON2WKOZSG44DEOBTHAZTKNI).
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
login manually, grab the Applications -> Cookies -> auth_token from inspect tab. insert it on ENV TWITTER_COOKIES=auth_token:YOUR-COOKIE |
Does the "YOUR-COOKIE" part (the actual auth token) have to be in quotes or anything? I'm still not able to log in to Twitter. |
lol no, just add: TWITTER_COOKIES=auth_token:xXXXXXXXX-XXXXXXX yes, you need "auth_token" and then : then your actual cookie token |
NVM I figured it out. Email address was wrong. |
i have the same issue and the cookie method doesn't work for me unfortunately. i also noticed that i get an email with the confirmation code when i run the agent and it tries to log in do you happen to have any other ideas how to solve that? i noticed that when i tried automating a different (test) account, it worked perfectly (and i did it from the same network, computer, etc.). it must have something to do with twitter's flagging of the account i guess |
i found a solution! what u need to do is: |
This should be marked as the solution, only thing that has worked so far! |
Describe the bug
I am trying to deploy eliza on gce, however i am getting error on authentication error 399 when logging in causing the login to fail.
To Reproduce
Expected behavior
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: