Publicize on Facebook: Featured image random issue

Hi there!

There are a couple of things happening here.

When I run a diagnostic check of your Jetpack connection, this is the error:

cURL error 52: Empty reply from server

This means that when we make a request to your server to fetch data for your site, the server is replying with no data. This is usually due to a firewall or a proxy put in place by your host. Can you reach out to them and ask that they look into this for you?

If there are any blocks or limits on your site’s xmlrpc.php file, please ask that they remove those.

In looking at the code for your posts, the theme is defining the OG tags, which is what we use to send data to Facebook and Twitter. It’s possible that these tags aren’t being created properly. Can you disable those tags in the theme so that the site will use Jetpack’s OG tags?

If you’re not sure how to do that, you can also install this plugin to force the site to use our tags:

https://www.ads-software.com/plugins/always-use-jetpack-open-graph/

Let me know how all of that goes ??

Hi,

Thanks for your help.

For the servers, I will ask (but it will not explain why it is random).
For the xmlrpc, I didn’t block or limit it.
For the theme, it’s Divi from Elegant Theme. Maybe it could be the cause… but I don’t remember an option to disable the tags. So I will use the plugin you suggested and see what happend next times I will published a post.
i will let you know.

For the servers, I will ask (but it will not explain why it is random).

It could be intermittent blocks or limits. If that is the case, then the Jetpack connection would work sometimes but not others, causing the random behavior that you’re seeing. Please let them know of that error so that they have more information to work with.

For the xmlrpc, I didn’t block or limit it.

It’s possible that your host has done so. Please ask them to check into this for you as well.

ok but, the problem is some parts of the publication are always ok (begining of the text/article, link to the post) and some are ramdom (feature image, excerpt…). Why half of a request would be executed sometimes? And sometimes fully executed…
I’m not a dev so maybe I’m wrong but not sure to understand the logic behind that.

But if the plugin doesn’t work, I will ask for sure to my host.

• This reply was modified 6 years, 7 months ago by golfloire.

These are questions that we can likely answer once we get the connection to Jetpack working. Without a working connection, it’s hard to know if there’s anything else that might be causing troubles here.

I just checked the connection again and I’m still seeing that same error.

If you could reach out to your host and let them know about this, they should be able to get you some more information.

Let me know how that goes.

Hi,

I asked them a few minutes ago. As soon as I have an answer I will let you know.
Thanks for your help.

They answered me.
It seems there’s nothing wrong the server configuration.
However, they made a slight modification (maybe it could help).
They want to know what kind of procedure/diagnostic you did to have the cURL error in order to check on their side what could be the issue.

Hi there! From what our debugger is returning to us, it seems like there are some issues happening on your xmlrpc.php file, as if something is blocking the communication. Jetpack can’t connect if it can’t reach this file.

It’s possible that there’s a limit in place for the number of connection attempts per minute. So even if the file is accessible and seems to be okay at the moment, if the settings are set to allow only 5 requests per minute, Jetpack can’t work properly.

Hope that can help! You can pass this info to your host and see what they say. If you prefer to continue the conversation in private to keep sensitive info private. you contact us via this contact form – don’t forget to mention this thread ??

Correct me if I’m wrong but XML-RPC is used by Publicize, not only to post on Facebook but also on the other social networks, right?
As it works FLAWLESSLY with Twitter (https://twitter.com/golfloire), I don’t think the issue is related to XML-RPC.

In case of you latest post, for example, Publicize worked well both on Facebook and Twitter.

That reinforces my theory that the xmlrpc connection issue you’re having might be intermittent and thus affecting Publicize intermittently, with more impact on Facebook.

Unfortunately I still can see the same error coming out from the xmlrpc.php file, so your host’s changes didn’t make any improvement ??

The error is the same: cURL error 52: Empty reply from server
Can you pass that to your host once again for me?

Also, check for any security/caching plugin you may have enabled, and try temporarily disable them, to see if it fixes the problem. You may also want to search for any firewall on your server side that might be blocking the communication with the xmlrpc.php file – your host again should be able to help you with that.

I know it might feel like we’re going in circles with that, so if you want to start investigating deeper on that please contact us directly (and please mention this thread) so we can also share info we can’t disclose publicly.

Thanks again in advance for your cooperation in sorting that out with us!

Since my initial report, I installed the plugin you adviced me for the tags. And with the 2 posts we published there was no errors… but I will wait a few more posts before saying it’s repared…

For xmlrpc… there is no “more impact” on Facebook… All the impact is on Facebook…
The success rate on twitter is 100%. It NEVER happened to fail.
For Facebook, the success rate is 66%…
The problem is ONLY with Facebook.

For the cURL error, our host would like to know what’s the request you sent to have the error. Do I have to contact you directly to have the procedure you use?

For the caching, it was one of my first suspect. At that time I was testing Comet Cache. I get back to WP Super Cache and it changed nothing. I’m think WP Super Cache is fully compatible with Jetpack ??

For the security, it’s mainly our host and they say nothing seems to block. But maybe if they know how you get these errors, they will find something.

Thanks for your help

• This reply was modified 6 years, 7 months ago by golfloire.

For xmlrpc… there is no “more impact” on Facebook… All the impact is on Facebook…

I think that’s just the symptom of the problem. When we’re sending the post information to your social media sites, it’s being sent to Twitter first and then due to the intermittance of the connection, it’s failing before we fully send the information to Facebook.

For the cURL error, our host would like to know what’s the request you sent to have the error. Do I have to contact you directly to have the procedure you use?

For this, we’re making a post request to your site’s xmlrpc.php file and getting that Empty reply error. Is the host able to make cURL POST requests without problems?

If so, they may need to whitelist us. Can you ask that they whitelist all connections to and from *.wordpress.com? If they request specific IP address, you can find the full list here:

https://jetpack.com/support/hosting-faq/

I’m think WP Super Cache is fully compatible with Jetpack

You are correct! We develop both plugins here so we do make sure that they work well together.

Let us know how that goes!

Thanks for your answer.
I transmitted the infos to our host.
I will let you know what they will answer to me.

Just a quick note about the Tags Plugin: after 4 successfull posts, the fifth is missing the featured image, excerpt, etc… so it’s not a tag problem…

I still wait for our host answer ??

I just have the answer from our host:

Jetpack is on the white list but they will check if the IP address changed recently.
They would like you to do another request/test in order for them to check the errors logs and see what could be wrong.
Please, tell us the time you did the new test in order to find it easily in the logs.
Thanks for your help