I’m sorry to hear you’ve run into issues.
Could you check your server error logs around the time when you experienced the issue, to find out more about the error?
If you don’t know how to access your server error logs, your hosting provider should be able to help.
Let me know how it goes.
The debug of jetpack say:
Parece que su sitio no se puede comunicar correctamente con Jetpack.
SELF:
Array
(
[headers] => Array
(
[server] => nginx
[date] => Mon, 21 Sep 2015 14:33:57 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 _dfw
)
[body] => {“error”:”Jetpack not connected”,”error_description”:”We were unable to find a Jetpack instance on your site. Please connect Jetpack to your WordPress.com account from within your WordPress admin.”}
[response] => Array
(
[code] => 400
[message] => Bad Request
)
[cookies] => Array
(
)
[filename] =>
)
Did you have a chance to look at your server error logs to find out more about the problem? Jetpack’s debug won’t help us much here, I’m afraid.
