“Jetpack could not contact WordPress.com: register_http_request_failed.”

After reading posts online like this one: register_http_request_failed … SSL connection timeout (WordPress forums) I realized that the issue was in fact an SSL connection timeout from your WordPress host to the Jetpack server. In my particular case it was a firewall issue as the Jetpack server did not pass the https validation. My guess is that back in the day Jetpack used the wildcard certificate from WordPress and as it had a WordPress.com domain there were no problems. Right now if you visit: https://jetpack.wordpress.com/jetpack you´ll see that Jetpack has the Jetpack.me domain and that it uses the *.WordPress.com certificate. The firewall on my web server then noticed the mismatch and threw the error above. After adding an exception to this certificate things worked again.

Enhanced by Zemanta

You may also like...

3 Responses

  1. James House says:

    Which firewall are you using? Would you mind elaborating on how you added the exception for the certificate?

    • JCarlos says:

      I´m using Microsoft’s Forefront Threat Management Gateway. There they have a section for https validation and a tab for exceptions. I added *.wordpress.com to the list of exceptions and indicated that I wanted to perform no validation on those sites. If you can try to see on your firewall the communication from the webserver and analyze it to see what is failing. In the case of TMG I had an https-inspection failure whose error code indicates a certificate validation issue.

  1. January 23, 2013

    […] more googling I found this post which indicated it might be something to with the jetpack/wordpress SSL certificate rather than […]

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.