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

Calls to this api have exceeded the rate limit. (613) #527

Open
brianjmurrell opened this issue Dec 8, 2021 · 1 comment
Open

Calls to this api have exceeded the rate limit. (613) #527

brianjmurrell opened this issue Dec 8, 2021 · 1 comment

Comments

@brianjmurrell
Copy link

I am using the latest, 0.9.6 release of this project but when I try to connect to Facebook Messenger with Pidgin I am getting:

(09:11:03) account: Connecting to account [redacted].
(09:11:03) connection: Connecting. gc = 0x55d66b7ae2f0
(09:11:03) http: Performing new request 0x55d66b16d690 to b-api.facebook.com.
(09:11:03) dnsquery: Performing DNS lookup for b-api.facebook.com
(09:11:03) dns: Wait for DNS child 1532899 failed: No child processes
(09:11:03) dns: Created new DNS child 1533802, there are now 1 children.
(09:11:03) dns: Successfully sent DNS request to child 1533802
(09:11:03) dns: Got response for 'b-api.facebook.com'
(09:11:03) dnsquery: IP resolved for b-api.facebook.com
(09:11:03) proxy: Attempting connection to 2a03:2880:f10d:83:face:b00c:0:25de
(09:11:03) proxy: Connecting to b-api.facebook.com:443 with no proxy
(09:11:03) proxy: Connection in progress
(09:11:03) proxy: Connecting to b-api.facebook.com:443.
(09:11:03) proxy: Connected to b-api.facebook.com:443.
(09:11:03) 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
(09:11:03) nss: subject=CN=*.facebook.com,O="Facebook, 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
(09:11:03) nss: partial certificate chain
(09:11:03) certificate/x509/tls_cached: Starting verify for b-api.facebook.com
(09:11:03) certificate/x509/tls_cached: Checking for cached cert...
(09:11:03) certificate/x509/tls_cached: ...Found cached cert
(09:11:03) nss/x509: Loading certificate from /home/brian/.purple/certificates/x509/tls_peers/b-api.facebook.com
(09:11:03) certificate/x509/tls_cached: Peer cert matched cached
(09:11:03) nss/x509: Exporting certificate to /home/brian/.purple/certificates/x509/tls_peers/b-api.facebook.com
(09:11:03) util: Writing file /home/brian/.purple/certificates/x509/tls_peers/b-api.facebook.com
(09:11:03) nss: Trusting CN=*.facebook.com,O="Facebook, Inc.",L=Menlo Park,ST=California,C=US
(09:11:03) certificate: Successfully verified certificate for b-api.facebook.com
(09:11:03) http: Request 0x55d66b16d690 performed successfully.
(09:11:03) connection: Connection error on 0x55d66b7ae2f0 (reason: 0 description: Calls to this api have exceeded the rate limit. (613))
(09:11:03) account: Disconnecting account [redacted] (0x55d6670c0d20)

But given the error above, this account sits in the disconnected state pretty much permanently and has been for weeks now, so I cannot actually be calling the API too many times.

I can log into FB and use Messenger there with no problems.

@brianjmurrell
Copy link
Author

No ideas here? I wonder why I can be the only person with this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant