Jetpack could not contact WordPress.com: register_http_request_failed

Operation timed out after 15001 milliseconds with 0 bytes received]

Jetpack uses your site’s XML-RPC file to communicate with WordPress.com. Unfortunately, access to that file is really slow at the moment:
http://kurakaniz.com/xmlrpc.php

In most of my tests, it took between 15 and 30 seconds to access that file:

$ curl -w "@curl-format.txt" -o /dev/null -s "http://kurakaniz.com/xmlrpc.php"
    time_namelookup:  0.161
       time_connect:  0.162
    time_appconnect:  0.000
   time_pretransfer:  0.162
      time_redirect:  0.000
 time_starttransfer:  22.254
                     ----------
         time_total:  22.254

I would recommend that you contact your hosting provider and ask them if they currently block or restrict access to your site’s XML-RPC file. If they don’t, they’ll need to run some tests to make sure it can be accessed quickly enough for third-party services to be able to make requests to the file.

I hope this helps.

Changing the file’s permissions won’t help, I’m afraid. The file is there, and is accessible. It just takes too long for a third-party service like WordPress.com to access the file.

You can reproduce the issue on your end by accessing the file in your browser
http://kurakaniz.com/xmlrpc.php

When I tried to access the file today, it took 33 seconds for the page to load.
http://i.wpne.ws/fV6E

It has to load way faster to be of any use.

On WordPress.org, for example, the file can be access in less than 500ms:
https://wordpress.org/xmlrpc.php
http://i.wpne.ws/fVZ7

If you forward those results to your hosting provider, they should be able to look into this issue for you.

But i am having issue in my main domain. when ever i tried to activate, deactivate or configure some modules and click on each module i am redirected to wordpress dashboard. plesee help.

Could you let me know the site URL, so I can take a closer look?

Thanks!

Thanks. I don’t notice anything wrong on that site at the moment.

Do you use a caching plugin on that site? If so, could you try to flush your cache, and see if it helps?

If you use a redirect plugin, it might also be worth deactivating it for a few minutes, and see if it helps.

Let me know how it goes.