related post

Could you try to install and activate this small plugin, by going to Plugins > Add New > Upload in your dashboard:
https://i.wpne.ws/Vdoc

Once you’ve activated the plugin, try to relaunch the indexation (you’ll find the reindex button by clicking on the “Debug” link at the bottom of the Jetpack menu in your dashboard).
If the Related Posts start appearing, you can deactivate and delete this small plugin.

Let me know if it helps.

i am doing it now

we use hhvm and nginx no cache

i have a strange message like the site can not communicate with wp
SELF:
Array
(
[headers] => Array
(
[server] => nginx
[date] => Fri, 10 Jul 2015 17:41:28 GMT
[content-type] => text/plain;charset=utf-8
[connection] => close
[x-pingback] => https://jetpack.wordpress.com/xmlrpc.php
[expires] => Wed, 11 Jan 1984 05:00:00 GMT
[cache-control] => no-cache, must-revalidate, max-age=60
[pragma] => no-cache
[x-hacker] => Jetpack Test
[x-ac] => 3.ams _sat
)

[body] => {“error”:”Could not fetch your site data”,”error_description”:”We were unable to fetch the data from your Jetpack-powered site, the communication channel seems to be broken.”}
[response] => Array
(
[code] => 400
[message] => Bad Request
)

[cookies] => Array
(
)

[filename] =>
)

https://myfrenchcity.com/floride/famille-floride/suivre-un-double-programme-francais-et-americain-coconut-grove/
work

https://myfrenchcity.com/edition-nationale/sintaller-aux-usa/immigration-usa/ou-retrouver-des-francophones-a-new-york/
No

like the new pages are not working maybe due to the connection problem
but i can access to the file
XML-RPC server accepts POST requests only.
i have never really check the debugg in jetpack so do not know if this is the host

ALSO WE ARE ON MULTISITE

i think the plugin fixed the pb

but i do not know why i can not communicate

i think the plugin fixed the pb

Excellent! I’m glad to hear that!

but i do not know why i can not communicate

You can ignore that warning. It’s a false positive, and only appears because you’ve disabled the Stats module. We’ll get that fixed in a future release.