-
Notifications
You must be signed in to change notification settings - Fork 66
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
Two factor authentication #163
Comments
For the moment, I turned off 2FA, logged in using messer, then turned it back on - I wonder if this will be a long-term solution or not, I'll come back with updates |
@nagylilla96 I guess that's hassle because... when you turn off your 2FA you will setup it again and again whenever you stop using this messer. I guess app password would work which is doesn't require any 2FA |
I have the same problem, but I can't log in even after I turned off 2FA, are there any extra steps? |
I'm not seeing app passwords working for me |
@gileswells I tried it .... seems I agree it doesn't work even you use app passowrds. |
Summary
Two factor authentication is always working - a text message with the code is not always sent, and when it is, the following message is displayed:
Failed to login: Error retrieving userID. This can be caused by a lot of things, including getting blocked by Facebook for logging in from an unknown location. Try logging in with a browser to verify.
Motivation
I saw this fixed in #16 but I think details about how 2FA works should be added to the README file, and probably the API has changed since then, because I still cannot log on using 2FA sadly :( I would not like to remove 2FA only to use this solution.
Whenever a login attempt is made from the cli, I get a notification that an unrecognized device is attempting to log in, and if I save it, the next attempt still displays this message, so in the end, all these devices will be recognized by Facebook as separate ones, and 2FA will not work.
I also find it weird how the displayed browser is
Safari for Mac OS X 10.10
on Facebook.The text was updated successfully, but these errors were encountered: