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

Bug: Twitter Authentication fails on Cloud. Error 399 #2225

Open
yongkangc opened this issue Jan 13, 2025 · 9 comments
Open

Bug: Twitter Authentication fails on Cloud. Error 399 #2225

yongkangc opened this issue Jan 13, 2025 · 9 comments
Labels
bug Something isn't working

Comments

@yongkangc
Copy link

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.

{
  "errors": [{
    "code": 399,
    "message": "Incorrect. Please try again. g;173669734519940919:-1736697345244:ILSZ2qNWESdWgKjC1KLSxaWZ:8"
  }]
}

To Reproduce

Expected behavior

Screenshots
image

Additional context

@yongkangc yongkangc added the bug Something isn't working label Jan 13, 2025
Copy link
Contributor

Hello @yongkangc! Welcome to the elizaOS community. Thank you for opening your first issue; we appreciate your contribution. You are now an elizaOS contributor!

@AIFlowML
Copy link
Collaborator

AIFlowML commented Jan 13, 2025 via email

@rferrari
Copy link
Contributor

login manually, grab the Applications -> Cookies -> auth_token from inspect tab.

insert it on ENV TWITTER_COOKIES=auth_token:YOUR-COOKIE

@squintdev
Copy link

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.

@rferrari
Copy link
Contributor

lol

no, just add:

TWITTER_COOKIES=auth_token:xXXXXXXXX-XXXXXXX

yes, you need "auth_token" and then : then your actual cookie token

@squintdev
Copy link

squintdev commented Jan 13, 2025

NVM I figured it out. Email address was wrong.

@karolproksa
Copy link

lol

no, just add:

TWITTER_COOKIES=auth_token:xXXXXXXXX-XXXXXXX

yes, you need "auth_token" and then : then your actual cookie token

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

@karolproksa
Copy link

i found a solution!

what u need to do is:
1/ go to the agent's twitter -> settings -> security and account access -> security -> two-factor authentication
2/ enable Authentication App
3/ click the button under the QR code to view it as string (it's 16 uppercase letters and numbers) - this is your 2FA SECRET
4/ complete the 2fa setup with an app like google authenticator
5/ add the 2fa secret to your .env file like this:
TWITTER_2FA_SECRET="YOUR_SECRET_CODE"

@AdamCuellar
Copy link

i found a solution!

what u need to do is: 1/ go to the agent's twitter -> settings -> security and account access -> security -> two-factor authentication 2/ enable Authentication App 3/ click the button under the QR code to view it as string (it's 16 uppercase letters and numbers) - this is your 2FA SECRET 4/ complete the 2fa setup with an app like google authenticator 5/ add the 2fa secret to your .env file like this: TWITTER_2FA_SECRET="YOUR_SECRET_CODE"

This should be marked as the solution, only thing that has worked so far!

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

6 participants