Jetpack could not contact token_http_request_failed. This usually means something is incorrectly configured on your web host.

For me it turns out that PHP is, as expected, fine – and the problem lies with the (external) transport that WordPress is trying to use. And it also turns out that there is a developer plugin which allows easy updating of the transports available to WordPress. The solution that worked for me was:

  1. Either manually download and install the Core Control plugin, or use the WordPress web-interface to search for “core control” and install the plugin automatically;
  2. Activate the new plugin, which will add a “Core Control” option to the Tools side-bar menu for Admin users – select this option;
  3. You should now see a page with a list of several modules – tick the “HTTP Access Module” and click “Save Module Choices”;
  4. A new link will then appear at the top of the same page, next to “Main Page”, named “External HTTP Access” – select this;
  5. From the first section of options, select “Disable Transport” for “cURL“.

At this point, Jetpack will now allow registration and finally stop nagging!

It is worth noting, however, that having cURL disabled prevents Akismet from being able to contact its servers, so once Jetpack is registered the above sequence should be reversed to re-enable cURL and, to be safe, disable Core Control so as not to accidentally break anything else. Once registration has been successful, Jetpack seems to be happy to continue working even with cURL as the active transport.


  1. Oral says:

    Thank you, but my question is this: What is the problem about server? Is there a way to learn it and fix it?

  2. Aru Martino says:

    thanks, it works great!

  3. ivan says:

    Thank you! It works :)

  4. ningnong says:

    thanks, it works great! :)

  5. Em says:

    January 2014, WP 3.8 with jetpack.2.7 and it still works. Thank you!

  6. thank so much, it work!

  7. […] who had the same problem but never had it resolved. :/ that sucks! I finally stumbled upon this: Mo Ghaoui, Personal Blog. This solution worked for me and was incredibly […]

  8. Riswan R says:

    Thanks, it’s work beautifully!

  9. Trevor says:

    This fixed my problem quickly and easily, thank you very much!

  10. Steven says:

    Thank you! Worked perfectly with Version 3.5.1!

  11. Massimo says:

    That worked for me too, thanks a lot.

  12. Guilherme Carvalho says:

    Thank you very much! 2

  13. Ricky Yip says:

    Thank you very much!
    It has solved my problem.

Leave a Reply

Your email address will not be published. Required fields are marked *