Error Activating Jetpack Plugin

When I went to activate the Jetpack plugin by WordPress.com for this site it rudely refused! I’d never came across this issue on any of my previous WordPress set-ups.

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

SSL certificate problem: self signed certificate in certificate chain

I also had an issue activating the Google Analytics plugin, when trying to assign / authenticate it to my Google account I received the Error: Invalid Token

The solution for me was to temporarily disable the cURL function on the site which then allowed me to activate the Jetpack plugin and authenticate Google Analytics plugin with my Google account. To do this please follow these steps:

1. Install and activate the Core Control plugin

2. Now under Tools click Core Control

3. Tick ‘HTTP Access Module 1.0’ and click ‘Save Model Choices’

4. At the top of the page under the Core Control title click on ‘External HTTP Access’

5. Under ‘Manage Transports’ find ‘cURL’ and click ‘Disable Transport’

6. Now activate the Jetpack plugin with your WordPress.com account as well as associating / activating your Google Analytics plugin with your Google account if required

7. Once verified that the Jetpack plugin has activated successfully you can go back in Core Control and activate the cURL transport, the same way as you deactivated it. The Jetpack and Google Analytics will continue to work once cURL is activated again, it’s just an issue during activation.

Hope this helps & take it easy!

 

This entry was posted in Jetpack, WordPress. Bookmark the permalink.

52 Responses to Error Activating Jetpack Plugin

  1. hgoor says:

    Man that was such a find! I had the exact same problem and it was driving me nuts. Good thing I found your solution using Google! How did you figure out this solution anyway? The errors seemed quite random?

    • Tim says:

      Excellent, glad this helped someone else as it took me a while just piecing it all together and I couldn’t find anyone else who had exactly the same problem! Rather random, it’s only ever happened to one of my WP sites before. Cheers for letting me know it worked for you too.

  2. Thanks for posting this! I ran into this problem as well and I would of had a horrible time trying to figure it out without this post. Cheers!

  3. Kenta says:

    Thanks for the great post! Helped me out without any problems! Kind of bothered me a bit:) I’ve been trying several hours to get it working, and your post helped me out. I also have a slow page, would love to have any great tips in optimizing your wordpress for speed on a home server. Thanks again

  4. quentin says:

    Thanks.

  5. wvanstraalen says:

    Thank you so much for this little trick!

  6. donholt says:

    Thank you! I was pulling my hair out until I stumbled on your “trick”!

  7. Ralph says:

    I tried your solution but got the following message – any ideas:

    “Your website needs to be publicly accessible to use Jetpack: site_inaccessible

    Error Details: The Jetpack server was unable to communicate with your site [IXR -32300: transport error: http_request_failed connect() timed out!]”

  8. nathantreid says:

    Thanks! This saved me quite a bit of frustration.

  9. Andrew says:

    Thanks bro, helped me alot too!

  10. Rob Attfield says:

    Have been wondering what the cause of this was for the longest time… Installing JetPack on another blog worked perfectly, but not on my current one. Am so glad to get JetPack working again – in my opinion it is the best plugin for seeing visitor stats – thanks for providing the “life-saving” solution!

  11. greensworld says:

    THANK YOU – just what I needed, could not find help on wordpress.com or any other website 🙂

  12. JP Senior says:

    Confirmed – this worked well for us. This seemed to have nothing to do with the certificate actually being self-signed: I confirmed under wireshark that the certificate was *.wordpress.com and was properly trusted by the computer CA chain. Seems like a php-specific issue, not a wordpress issue. Nonetheless this workaround was great.

  13. mattb007 says:

    Awesome!!! Thanks 🙂

  14. Chaunette says:

    After following your instructions, my site is connected to Jetpack! Thank you very much!

  15. Todd says:

    Thank you!

  16. kayatnight says:

    hi, I was so hoping this would work, but alas I got this error:
    Your website needs to be publicly accessible to use Jetpack: site_inaccessible Error Details: The Jetpack server was unable to communicate with your site [HTTP 404]. Ask your web host if they allow connections from WordPress.com. If you need further assistance, contact Jetpack Support: http://jetpack.me/support/

    any ideas?
    Thanks,
    Karin

    • mark says:

      Hey
      The answer is in the error message. HTTP 404 ERROR means that your website is not “live” on the internet. If you are running server in your home or business you need to make sure that you have “port forwarding” setup on your router. (IP address of your server, and HTTP port 80

  17. pnatel says:

    Good stuff!
    Worked as a charm!

  18. tvactress says:

    dint work sorry , plz give any other methods

  19. Nicolas says:

    Thanks, it did work !

  20. Pingback: 워드프레스 Jetpack 플러그인 설치 후 활성화 안 되는 오류 해결 | baada Library

  21. webrabauken says:

    Thanks for that tip! Helped me a lot!

  22. Martin says:

    thank you very much!

  23. Pingback: » Error Activating Jetpack Plugin on Azure Keep Calm and Code On

  24. Thank you so much – you’ve really helped.

  25. Pingback: WordPress on Azure | P3

  26. Raymond says:

    Thank you so much!!!

  27. samuelr2010 says:

    thanks, it worked as described !

  28. So, between those two posts I decided to try hacking jetpack.php as mentioned in the wordpress forum post, which as the poster suggests, seems to fix the problem. While wordpress are silent on what the actual resolution is for this, I can confirm that changing –

    defined( ‘JETPACK__API_BASE’ ) or define( ‘JETPACK__API_BASE’, ‘https://jetpack.wordpress.com/jetpack.’ );

    to

    defined( ‘JETPACK__API_BASE’ ) or define( ‘JETPACK__API_BASE’, ‘http://jetpack.wordpress.com/jetpack.’ );

  29. Pingback: Wordpress på 5 minutter | thea.us.to

  30. Pingback: Jetpack for WordPress na serwerze Synology - CoSTa's Family Page

  31. I really can’t express my gratitude enough to you because this saved me a LOT of WORK. I was about to give up on either Azure or JetPack!

    I’m really, really curious to know how was the train of thought that lead you to this solution.

    I think that updating the article with this info will help a LOT of people to solve similar problems.

    Best wishes and thank you again (and again, and again…)

    • As a follow up: I was having trouble adding a new Facebook Connection and I just deactivated again the cCurl transport and it worked…

      In other words: everything that requires HTTPs is not working, at least on an Azure-based website. I believe that Microsoft IIS has some very strange configuration of certificates which is breaking the standard behavior of wordpress secure transports… It is a shame I really know nothing at all about wordpress programming to debug it and find the problem and perhaps contact the AZURE team to iron it out for everybody.

  32. Pingback: Moving the blog to Azure Web Sites | Stefan Johansson

  33. Pingback: Fixing Twitter Problems in Azure WordPress Hosting | Can I change this later???

  34. Mick says:

    Legend thanks for the post, my Windows Azure WP sites were driving me crazy!! JetPack is all connected and working perfectly

  35. zoobiewa says:

    Wow. Incredible. I can’t believe how many plugins I’ve been having to install to get something simple working, but thank you for figuring this out.

  36. Pingback: Blog MUP | Instalar y activar JetPack en tu blog de Wordpress hospedado en Windows Azure

  37. Pingback: Connecting the Jetpack plugin | Isaac McGarvey

  38. mclschwerinersalon says:

    Great! Thank you so much.
    Worked perfect for me.

  39. lencoint says:

    Thanks for this, resolved my problem!

  40. Great thanks! Works well for me

  41. Legend. Worked for me too. Was a bit apprehensive about using the outdated plugin, but… all went great.

  42. Canon says:

    I had the same problem. Thanks for help.
    Sara

Leave a Reply