Hi @bluemoth, could you try removing Jetpack from the Facebook settings at https://www.facebook.com/settings/?tab=business_tools, and then reconnect Jetpack Social to it?
If the problem persists, please check if there are any security plugins activated that might be blocking requests from Jetpack. Also try contacting your hosting provider and ask them to check the security logs to see if they might be blocking or throttling access.
Hi @bluemoth,
Do you have updates about that? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!
Hi there, we have made the suggested changes and are waiting to see if the fix holds. Thank you!
Hi @bluemoth,
Great news, thanks for sharing! I’m going to mark this thread as solved. If you have any further questions or need more help, you’re welcome to open another thread here. Cheers!
Unfortunately the problem remains – we tried everything that you said. The social posts work/go through for about a week and then stop. Please advise next steps and thank you.
Hi @bluemoth,
Did you check whether there are any security blocks with your hosting provider? Jetpack is getting into some roadblocks when it tries to communicate with your website; however, I am afraid we can’t see the specific cause since it is happening behind the scenes.
Hi there,
Yes I did – my host at WP Engine confirmed that they are doing nothing to prevent JetPack from any connections. The social connections work for a few days and then stop. We have removed AUTH, disconnected, reconnected, re-authed, etc. and nothing works. The problem persists.
Thank you and please advise.
BMC
Hi @bluemoth,
Upon further inspection of your site, it’s clear that there is an intermittent blockage preventing Jetpack from establishing a consistent connection. At the time of this writing, the connection is entirely severed. Our logs point to something on the server side, possibly a firewall or security setting, or even a security plugin, given this specific error we encountered:
http_request_failed: cURL error 28: Operation timed out after 5003 milliseconds with 0 bytes received
Additionally, I conducted a rate limit test which shows a series of 504 Gateway Timeout errors, followed by a set of successful 200 OK responses. This pattern suggests that rate limiting may be occurring at the server level, even if unintentionally.
Here are a few steps you can take:
- Detailed Error Logs: Request detailed error logs from your host during the time window when the disconnection occurs. This can sometimes reveal hidden issues not shown in standard logs.
- Server Configuration: Verify your server’s configuration for any rate limiting or security features that might affect outbound connections, specifically ones that might target the frequency or volume of requests.
- Additional Security Plugins: If you’re using additional security plugins, temporarily disable them to test if the connection stabilizes. If it does, you can pinpoint which plugin is causing the issue.
- Extended Timeout Settings: Increase the timeout setting on your server for outgoing HTTP requests. The current limit seems to be around 5 seconds, which may be too short for some operations.
Let’s tackle these steps to see if we can isolate the issue.
Thank you, and I look forward to your update.
