Opened 5 years ago

Closed 4 years ago

#15589 closed defect (worksforme)

Facebook "Not Authorized"

Reported by: bwat47 Owned by: deryni
Milestone: Component: XMPP
Version: 2.10.7 Keywords:
Cc: bjoernv, kroeckx, devurandom

Description

This started happening the other day on all my computers, and I've seen it on multiple internet connections.

When I try to enable my previously working facebook account it just says "not authorized" every single time.

I think facebook may have changed something that broke pidgin.

Change History (31)

comment:1 Changed 5 years ago by bwat47

Forgot to mention: I did verify that I have the correct password. I have not changed my facebook password and this issue popped up out of the blue.

I'm using all the default facebook (XMPP) settings.

comment:2 Changed 5 years ago by Kvasi

Same happened to me, but when checking the settings for the account the "connect server" setting was empty, setting that again worked.

comment:3 Changed 5 years ago by shellholic

I confirm Kvasi's solution, in "avanced" tab of your facebook account settings, simply add "chat.facebook.com" in "connect to server:". I checked with a backup (in accounts.xml), it's new, it was not the case before yesterday.

comment:4 Changed 5 years ago by babop

I also confirm Kvasi's soltuion !

comment:5 Changed 5 years ago by deedee76_mikael62

I have been able to connect to FB, but I have NOT been able to see my friendslist. Can someone give me a lil advice plzzzzzz

comment:6 Changed 5 years ago by atlgator

I've seen this off and on for the last 5-6 weeks on my Pidgin clients. It has been working fine for a while but today it will NOT connect. I've verified all the default settings are right. I've verified chat.facebook.com is added on advanced tab. I've tried creating a new App Password on Facebook for this Pidgin client. But it keeps saying the client is Not Authorized. No idea how to fix this time....

comment:7 Changed 5 years ago by elieux

I'd also been unable to connect to Facebook Chat lately (maybe it was caused by a password change, I'm not sure about the order of events there). (Re-)Creating an App Password didn't help. Ultimately, I visited https://www.facebook.com/sitetour/chat.php and noticed "Password: <your Facebook password>" in the setup help, and I tried using my main Facebook password in Pidgin and surprisingly, I could connect.

I have two-factor authentication enabled, so this is certainly weird behavior -- why have App Password if they can't be used? -- but maybe Facebook decided to give XMPP a special treatment regarding passwords and maybe the change for my account was triggered by my password change.

Hope it helps someone.

comment:8 follow-up: Changed 5 years ago by atlgator

I had the same experience. I've had two-factor auth on for a while. I had App Passwords generated for each Pidgin install on multiple machines. Then they stopped working recently. I discovered last week that my normal FB password now works and the App Passwords do not. Seems like FB screwed up on the two-factor auth IMO....

comment:9 Changed 4 years ago by elieux

Today, Pidgin said I'm "not authorized" when I tried to log in to Facebook Chat (still using my main password). I tried several times, until I noticed my phone received an SMS for each attempt. The messages said "Use <numeric code> as your password for Facebook Chat." The code didn't work either, but it didn't generate another message. I left it like that.

Later today, I tried logging in again and this time I got a this message through Pidgin from chat.facebook.com: "Your account is temporarily unavailable. Regain access by logging into your account from a web browser." I have seen this in the past, so I went to Facebook web, confirmed that it wasn't a hack attempt and everything started working again.

I just wanted to share this, in case anyone else is experiencing this.

comment:10 Changed 4 years ago by joelj

I was getting this as well.

If you're using 'facebook.username' to log into Pidgin XMPP, do not log into Facebook on the web using your email address.

See this: http://radu.cotescu.com/facebook-pidgin-not-authorised/

comment:11 follow-up: Changed 4 years ago by petesky

Hi ! Since yesterday neither facebook username nor email is working to login via pidgin when using sms authorization code (2 factor) - any solution ?

comment:12 in reply to: ↑ 11 Changed 4 years ago by elieux

Replying to petesky:

Hi ! Since yesterday neither facebook username nor email is working to login via pidgin when using sms authorization code (2 factor) - any solution ?

I don't think the SMS code is working at all for Facebook XMPP.

Check Facebook in your browser if there's any "Unauthorized login attempt" notification. Try using your main Facebook password to log in.

comment:13 Changed 4 years ago by blubby

If you use 2-factor authentication, you need to create an application-specific password for Pidgin. Pidgin doesn't support 2-factor auth.

comment:14 follow-up: Changed 4 years ago by atlgator

Actually, my experience has been that Pidgin USED to work with an application-specific password. But then Facebook changed something and it stopped working. I couldn't get online for 2 weeks. Must have tried 20 different app-passwords on facebook.com. Finally tried my original FB password and it started working! Even though I have 2-factor enabled. This has worked for three months (since my post above). Over the last few days I started getting authenticate errors with my normal FB password. Then I'd receive an SMS from FB that has a # code to enter. Which I would put in Pidgin and it would work. Except a few hours later I'd get booted again. Then FB password would work again. Then I'd get the boot. Then it would send me a text with another # password, which would work for a little while. Rinse and repeat. I keep bouncing back and forth right now. I just tried the app-password thing again and it is DEFINITELY still not working for me. But this weird oscillation between my normal FB password and the 2-factor thing is working. Just a horrible PITA. Anybody else seeing this??

comment:15 in reply to: ↑ 14 ; follow-up: Changed 4 years ago by elieux

Replying to atlgator:

Anybody else seeing this??

Yeah, this sounds like some of the days I had in the last two weeks, except I don't think the SMS passcode ever worked with my account, so instead switching between that and the main password, I would go off-line for several hours until I decided to try again with my main password and Facebook decided to let me in. The "Unauthorized login attempt" notifications on Facebook seem to play a role here, but approving the login attempt seems to work only sometimes. It may be dependent on my location though. I mostly had problems when in office. During the past 8 days, I've stayed home and I recall only one boot here.

Last edited 4 years ago by elieux (previous) (diff)

comment:16 in reply to: ↑ 15 Changed 4 years ago by elieux

I don't think the SMS passcode ever worked with my account

I tried the SMS passcodes again and they seem to work. The yesterday's one lasted at least from morning till afternoon (I didn't use it this morning).

comment:17 in reply to: ↑ 8 Changed 4 years ago by pmouse

Replying to atlgator:

I had the same experience. I've had two-factor auth on for a while. I had App Passwords generated for each Pidgin install on multiple machines. Then they stopped working recently. I discovered last week that my normal FB password now works and the App Passwords do not. Seems like FB screwed up on the two-factor auth IMO....

Interesting. Any more information along this line of inquiry? Me too, but only just recently, which suggests it wasn't a global change on FB side. It was working last week AFAIK. I remember when my FB password stopped working for XMPP, then I created an "App" password just like you; that was in January 2013. Why would it just stop working now just for me?

Thanks for suggesting I try the regular FB password, btw.

Any one know why my "App" password stopped working? When they will work again?

comment:18 Changed 4 years ago by Skalman

I have the same problems and cannot sign in (either with app password or my main one) when two-factor auth is enabled.

Perhaps this is the time to contact somebody working at Facebook?

comment:19 Changed 4 years ago by Skalman

I submitted a bug report here.

comment:20 Changed 4 years ago by atlgator

Yeah, I've actually submitted a couple bug reports to Facebook over the last 3 months. No response.... :-\

comment:21 Changed 4 years ago by pmouse

Nope, spoke too soon. Neither my FB password nor my "App" password work, now. What a pain. Between this and Google deceitfully dropping XMPP support, I haven't any contacts left.

comment:23 in reply to: ↑ description Changed 4 years ago by JujuTh

I just installed Pidgin yesterday, and I'm getting the same error "Not Authorized" trying to connect my facebook account. I'm using simple authent. I checked again and again the password, and even tried to change it, but no success. Here is my log:

Pidgin Debug Log : 22/09/2013 14:17:33
(14:17:26) account: Connecting to account myuser@chat.facebook.com/Pidgin.
(14:17:26) connection: Connecting. gc = 055C0500
(14:17:26) dnsquery: Performing DNS lookup for chat.facebook.com
(14:17:26) dnsquery: IP resolved for chat.facebook.com
(14:17:26) proxy: Attempting connection to 173.252.107.17
(14:17:26) proxy: Connecting to chat.facebook.com:5222 with no proxy
(14:17:26) proxy: Connection in progress
(14:17:26) proxy: Connecting to chat.facebook.com:5222.
(14:17:26) proxy: Connected to chat.facebook.com:5222.
(14:17:26) jabber: Sending (myuser@chat.facebook.com/Pidgin): <?xml version='1.0' ?>
(14:17:26) jabber: Sending (myuser@chat.facebook.com/Pidgin): <stream:stream to='chat.facebook.com' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
(14:17:26) jabber: Recv (389): <?xml version='1.0' ?><stream:stream from='chat.facebook.com' id='1' version='1.0' xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' xml:lang='en'><stream:features><starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>X-FACEBOOK-PLATFORM</mechanism><mechanism>PLAIN</mechanism></mechanisms></stream:features>
(14:17:26) jabber: Sending (myuser@chat.facebook.com/Pidgin): <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
(14:17:26) jabber: Recv (50): <proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
(14:17:27) nss: subject=CN=chat.facebook.com,O="Facebook, Inc.",L=Palo Alto,ST=California,C=US issuer=CN=DigiCert High Assurance CA-3,OU=www.digicert.com,O=DigiCert Inc,C=US
(14:17:27) nss: subject=CN=DigiCert High Assurance CA-3,OU=www.digicert.com,O=DigiCert Inc,C=US issuer=CN=DigiCert High Assurance EV Root CA,OU=www.digicert.com,O=DigiCert Inc,C=US
(14:17:27) nss: partial certificate chain
(14:17:27) certificate/x509/tls_cached: Starting verify for chat.facebook.com
(14:17:27) certificate/x509/tls_cached: Checking for cached cert...
(14:17:27) certificate/x509/tls_cached: ...Found cached cert
(14:17:27) nss/x509: Loading certificate from C:\Users\me\AppData\Roaming\.purple\certificates\x509\tls_peers\chat.facebook.com
(14:17:27) certificate/x509/tls_cached: Peer cert matched cached
(14:17:27) nss/x509: Exporting certificate to C:\Users\me\AppData\Roaming\.purple\certificates\x509\tls_peers\chat.facebook.com
(14:17:27) util: Writing file C:\Users\me\AppData\Roaming\.purple\certificates\x509\tls_peers\chat.facebook.com
(14:17:27) certificate: Successfully verified certificate for chat.facebook.com
(14:17:27) jabber: Sending (ssl) (myuser@chat.facebook.com/Pidgin): <stream:stream to='chat.facebook.com' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
(14:17:27) jabber: Recv (ssl)(338): <?xml version='1.0' ?><stream:stream from='chat.facebook.com' id='1' version='1.0' xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' xml:lang='en'><stream:features><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>X-FACEBOOK-PLATFORM</mechanism><mechanism>PLAIN</mechanism></mechanisms></stream:features>
(14:17:27) sasl: Mechs found: X-FACEBOOK-PLATFORM PLAIN
(14:17:27) jabber: Sending (ssl) (myuser@chat.facebook.com/Pidgin): <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='PLAIN' xmlns:ga='http://www.google.com/talk/protocol/auth' ga:client-uses-full-bind-result='true'>password removed</auth>
(14:17:27) jabber: Recv (ssl)(1): <
(14:17:27) jabber: Recv (ssl)(92): failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-authorized/></failure></stream:stream>
(14:17:27) sasl: Mechs found: X-FACEBOOK-PLATFORM 
(14:17:27) sasl: No worthy mechs found
(14:17:27) connection: Connection error on 055C0500 (reason: 2 description: Non autorisé)
(14:17:27) account: Disconnecting account myuser@chat.facebook.com/Pidgin (01FCB600)
(14:17:27) connection: Disconnecting connection 055C0500
(14:17:27) jabber: Sending (ssl) (myuser@chat.facebook.com/Pidgin): </stream:stream>
(14:17:27) connection: Destroying connection 055C0500

comment:24 follow-up: Changed 4 years ago by elieux

Update: I have created a new App Password today for Pidgin and it worked.

comment:25 Changed 4 years ago by kroeckx

I used to be able to connect with the apps platform disabled. I now need to enable it. On connect it now also shows that I gave permission to use the app.

comment:26 in reply to: ↑ 24 ; follow-up: Changed 4 years ago by babop

Replying to elieux:

Update: I have created a new App Password today for Pidgin and it worked.

How did you do that? It would be nice to have at last the solution for everybody.

comment:27 in reply to: ↑ 26 ; follow-ups: Changed 4 years ago by Skalman

Replying to babop:

Replying to elieux:

Update: I have created a new App Password today for Pidgin and it worked.

How did you do that? It would be nice to have at last the solution for everybody.

I also created one today and it worked. Just to be clear:

  1. I have enabled 2-factor authentication ("Login Approvals").
  2. Account settings -> Security -> App passwords -> Generate app passwords -> Generate app passwords -> Enter "Instantbird"
  3. Use the generated password in Instantbird

I didn't have to change any settings to make this work.

comment:28 in reply to: ↑ 27 Changed 4 years ago by atlgator

Yes, this also started working for me a couple weeks ago. Previously this wasn't working or was unreliable (would work for a while and then stop). It's been stable for at least 2-3 weeks now. :-)

Replying to Skalman:

Replying to babop:

Replying to elieux:

Update: I have created a new App Password today for Pidgin and it worked.

How did you do that? It would be nice to have at last the solution for everybody.

I also created one today and it worked. Just to be clear:

  1. I have enabled 2-factor authentication ("Login Approvals").
  2. Account settings -> Security -> App passwords -> Generate app passwords -> Generate app passwords -> Enter "Instantbird"
  3. Use the generated password in Instantbird

I didn't have to change any settings to make this work.

comment:29 in reply to: ↑ 27 Changed 4 years ago by babop

Thanks a lot! It perfectly worked!

Replying to Skalman:

Replying to babop:

Replying to elieux:

Update: I have created a new App Password today for Pidgin and it worked.

How did you do that? It would be nice to have at last the solution for everybody.

I also created one today and it worked. Just to be clear:

  1. I have enabled 2-factor authentication ("Login Approvals").
  2. Account settings -> Security -> App passwords -> Generate app passwords -> Generate app passwords -> Enter "Instantbird"
  3. Use the generated password in Instantbird

I didn't have to change any settings to make this work.

comment:30 Changed 4 years ago by JujuTh

It works for me too, but it appears my problem was different (same symptom though). I finally found out that there is a setting in FB called "Turn Off Platform" under App Settings. This was OFF in my case, and now I turned it "On" and it works!

comment:31 Changed 4 years ago by datallah

  • Resolution set to worksforme
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!