Unknown error
usermyname12 opened this issue · 18 comments
It does not work anymore. It tries to connect and it fails with "An unknown error has occurred". Account gets locally disabled as well.
I'm having the same problem this morning. Facebook no longer connects. :(
Can confirm. It stopped working today.
Same issue as of 00:44:11 UTC 14 October 2023.
Windows 10 Pro 64-bit
Pidgin 2.14.1 (libpurple 2.14.1)
Content formerly available at https://github.com/ae-bogdan/libfacebook_pidgin is installed.
Debug of most recent re-attempt follows. Facebook Username, ID number, and Windows username redacted.:
(03:32:11) account: Connecting to account [REDACTED].
(03:32:11) connection: Connecting. gc = 05F96868
(03:32:11) http: Performing new request 05B1C278 to b-api.facebook.com.
(03:32:11) dnsquery: Performing DNS lookup for b-api.facebook.com
(03:32:11) dnsquery: IP resolved for b-api.facebook.com
(03:32:11) proxy: Attempting connection to 2a03:2880:f175:181:face:b00c:0:25de
(03:32:11) proxy: Connecting to b-api.facebook.com:443 with no proxy
(03:32:11) proxy: Connection in progress
(03:32:11) proxy: Connecting to b-api.facebook.com:443.
(03:32:11) proxy: Connected to b-api.facebook.com:443.
(03:32:11) nss: SSL version 3.3 using 128-bit AES-GCM with 128-bit AEAD MAC
Server Auth: 256-bit ECDSA, Key Exchange: 256-bit ECDHE, Compression: NULL
Cipher Suite Name: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
(03:32:11) nss: subject=CN=.facebook.com,O="Meta Platforms, Inc.",L=Menlo Park,ST=California,C=US issuer=CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US
(03:32:11) nss: partial certificate chain
(03:32:11) certificate/x509/tls_cached: Starting verify for b-api.facebook.com
(03:32:11) certificate/x509/tls_cached: Checking for cached cert...
(03:32:11) certificate/x509/tls_cached: ...Found cached cert
(03:32:11) nss/x509: Loading certificate from C:\Users[REDACTED]\AppData\Roaming.purple\certificates\x509\tls_peers\b-api.facebook.com
(03:32:11) certificate/x509/tls_cached: Peer cert matched cached
(03:32:11) nss/x509: Exporting certificate to C:\Users[REDACTED]\AppData\Roaming.purple\certificates\x509\tls_peers\b-api.facebook.com
(03:32:11) util: Writing file C:\Users[REDACTED]\AppData\Roaming.purple\certificates\x509\tls_peers\b-api.facebook.com
(03:32:11) nss: Trusting CN=.facebook.com,O="Meta Platforms, Inc.",L=Menlo Park,ST=California,C=US
(03:32:11) certificate: Successfully verified certificate for b-api.facebook.com
(03:32:13) http: Request 05B1C278 performed successfully.
(03:32:13) http: Performing new request 05B1C1D0 to graph.facebook.com.
(03:32:13) dnsquery: Performing DNS lookup for graph.facebook.com
(03:32:13) dnsquery: IP resolved for graph.facebook.com
(03:32:13) proxy: Attempting connection to 2a03:2880:f082:10d:face:b00c:0:2
(03:32:13) proxy: Connecting to graph.facebook.com:443 with no proxy
(03:32:13) proxy: Connection in progress
(03:32:13) proxy: Connecting to graph.facebook.com:443.
(03:32:13) proxy: Connected to graph.facebook.com:443.
(03:32:13) nss: SSL version 3.3 using 128-bit AES-GCM with 128-bit AEAD MAC
Server Auth: 256-bit ECDSA, Key Exchange: 256-bit ECDHE, Compression: NULL
Cipher Suite Name: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
(03:32:13) nss: subject=CN=.facebook.com,O="Meta Platforms, Inc.",L=Menlo Park,ST=California,C=US issuer=CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US
(03:32:13) nss: partial certificate chain
(03:32:13) certificate/x509/tls_cached: Starting verify for graph.facebook.com
(03:32:13) certificate/x509/tls_cached: Checking for cached cert...
(03:32:13) certificate/x509/tls_cached: ...Found cached cert
(03:32:13) nss/x509: Loading certificate from C:\Users[REDACTED]\AppData\Roaming.purple\certificates\x509\tls_peers\graph.facebook.com
(03:32:13) certificate/x509/tls_cached: Peer cert matched cached
(03:32:13) nss/x509: Exporting certificate to C:\Users[REDACTED]\AppData\Roaming.purple\certificates\x509\tls_peers\graph.facebook.com
(03:32:13) util: Writing file C:\Users[REDACTED]\AppData\Roaming.purple\certificates\x509\tls_peers\graph.facebook.com
(03:32:13) nss: Trusting CN=.facebook.com,O="Meta Platforms, Inc.",L=Menlo Park,ST=California,C=US
(03:32:13) certificate: Successfully verified certificate for graph.facebook.com
(03:32:13) http: Request 05B1C1D0 performed without success.
(03:32:13) connection: Connection error on 05F96868 (reason: 2 description: An unknown error has occurred.)
(03:32:13) account: Disconnecting account [REDACTED]
(03:32:13) connection: Disconnecting connection 05F96868
(03:32:13) connection: Destroying connection 05F96868
Can confirm, same thing happened to me today as well.
I tried updating to Facebook Fixed by 64kramsystem in hopes that it would make the issue go away, but sadly, it did not.
You might want to try using Caprine instead since this plugin is not maintained. https://github.com/sindresorhus/caprine
Caprine is Facebook only. I want a single application which supports all the protocols.
Yep. They must've changed something.
Looks like it's auth related, OAuth seems to be failing on Facebook's end:
POST /graphql HTTP/1.1
Host: graph.facebook.com
Connection: Keep-Alive
Accept: */*
Accept-Encoding: gzip, deflate
Content-Length: 286
Authorization: OAuth ...
(21:58:14) http: Got main header with code 500
(21:58:14) http: Got header: Content-Type: application/json; charset=UTF-8
(21:58:14) http: Got header: WWW-Authenticate: OAuth "Facebook Platform" "unknown_error" "An unknown error has occurred."
(21:58:14) facebook: HTTP Response (0x55bf4130dc60):
(21:58:14) facebook: Response Error: Invalid HTTP response code (500) (500)
(21:58:14) facebook: Response Data: {"error":{"message":"An unknown error has occurred.","type":"OAuthException","code":1,"fbtrace_id":""}}
Oh, so chances are it's just broken atm.
Also getting "An unknown error has occurred" and cannot connect. Please can somebody fix this?
The best thing going for Pidgin is that the chats are unified. I can communicate with a buddy on different protocols and still have a unified chat history.
Ferdium is a good alternative that supports many different protocols. Basically a wrapper around all their web apps but it’s better than all different clients running for sure.
…
Sent from my mobile device On Oct 14, 2023, at 6:43 AM, MAN-AT-ARMS @.> wrote: You might want to try using Caprine instead since this plugin is not maintained. https://github.com/sindresorhus/caprinehttps://github.com/sindresorhus/caprine Caprine is Facebook only. I want a single application which supports all the protocols. This plugin is Facebook only? — Reply to this email directly, view it on GitHub<#543 (comment)>, or unsubscribe<github.com/notifications/unsubscribe-auth/AAMUJBSAWDQ754VMNO632HDX7JUEXAVCNFSM6AAAAAA6ACYIVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRSHAYTIOJTHA>. You are receiving this because you are subscribed to this thread.Message ID: @.>
Can anybody recommend alternative app for this? I need Buddy pounces and invisible mode.
Ferdium is a good alternative that supports many different protocols. Basically a wrapper around all their web apps but it’s better than all different clients running for sure.
Please don't suggest any alternative application. Suggest an alternative plugin to Pidgin, but not an alternative application. There should be a rule against that.
Ferdium is a good alternative that supports many different protocols. Basically a wrapper around all their web apps but it’s better than all different clients running for sure.
Please don't suggest any alternative application. Suggest an alternative plugin to Pidgin, but not an alternative application. There should be a rule against that.
Please don't suggest that I shouldn't suggest an alternative application. Suggest that it's a shame that no one is able to maintain this plugin (or Pidgin itself for that matter, which I love and still use for whatever I can, such as Teams and WhatsApp), but not that I shouldn't suggest an alternative application, especially as an alternative plugin for Facebook Messenger does not exist, at least which I am aware of. There should be a rule against that.
Be advised at 03:40:33 UTC 15 October 2023 I had completely successful login to Facebook protocol with Pidgin. This session has been solid for about 90 min. Presence updates, pounce triggers, and messages in both directions working fine. My last (failed) attempt to login was very roughly 3 hours prior.
This problem self-resolved. I had yet to take any action apart from re-enabling the Facebook protocol from error state in Pidgin.
It's fixed for me as well, though I get ":1:12: feldolgozási hiba: unexpected identifier `taNewMessage', expected value" errors at times (usually when I send a message to someone through the browser).
But yes, finally, the "Unknown error" is fixed.
Whatever was the problem, it seems to have indeed solved itself without intervention. 2023-10-15 0723 hours UTC / Finland.
Can confirm too: The issue has resolved itself. :-)