WordPress.org

1. deigote
   Member
   Posted 7 months ago #
   

   Hi there.

   I'm trying to use last version of Jetpack in a self hosted wordpress that runs in Amazon EC2 and I'm obtaining the following when trying to connect to WordPress.com:

   Jetpack could not contact WordPress.com: register_http_request_failed. This usually means something is incorrectly configured on your web host.

   The blog has a plain wordpress installation with no other plugins and I switched to the default theme just in case that was the problem. I also SSHed the server and did the following (using the apache user that is the one running the Apache server that runs WordPress):

   apache@host ~ $ curl -i -L --data 'test' 'https://jetpack.wordpress.com/jetpack.register/1'
   HTTP/1.1 400 Bad Request
   Server: nginx
   Date: Fri, 26 Oct 2012 12:51:50 GMT
   Content-Type: application/json
   Transfer-Encoding: chunked
   Connection: keep-alive
   Vary: Cookie
   X-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header.
   X-Pingback: http://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
   
   {"error":"home_missing","error_description":"The required \"home\" parameter is missing."}

   It seems that the connection is being made without problems... What should I try next?

   Thanks in advance.

   http://wordpress.org/extend/plugins/jetpack/

2. Tim
   Jetpack Team Lead
   Plugin Author
   Posted 7 months ago #
   

   Could you download the Jetpack compatibility plugin, run it, and email the results to us at support@jetpack.me? http://plugins.trac.wordpress.org/export/617773/jetpack/branches/jetpack-compatibility-test.zip

   Do not post the results. The results may contain sensitive info, which we need for debugging, so please email them.

   Thanks!

3. deigote
   Member
   Posted 7 months ago #
   

   In case you are reading this, what was happening in my case was that the blog wasn't public yet - I was browsing it by modifying the hosts file.

   It looks that the communication must be possible in both ways, and I didn't recall about it after a while :-).

   Thanks a lot for your support and best regards.

Reply

You must log in to post.