The Jetpack server was unable to communicate with your site.

  • Resolved bluedrag

    (@bluedrag)


    6 years, 11 months ago

    I’ve just moved my site from http to https (different folders on the same server) and jetpack has stopped working since this change. When I try to click “connect” jetpack” to connect my site to my wordpress.com account I get this error after maybe 15-20 seconds of loading.

    Error Details: The Jetpack server was unable to communicate with your site https://alabama-music.com [IXR -32300: transport error: http_request_failed cURL error 28: Connection timed out after 10001 milliseconds]

    I’ve googled the issue and can’t seem to find anyone whose experienced the same error message.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there!
    When I run a diagnostic test on your Jetpack connection, I get the following error instead: “cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received”, which is not the same you got, but something somehow similar.

    This usually means that your web host is blocking some connections Jetpack needs in order to work correctly.

    I also tried to access to your site by using the HTTP and when doing it the page returns an alert/error message as opposed to point to your HTTPS site (which looks down at the moment)

    Could you please contact your web host and ask them to make sure that the connections to and from *.wordpress.com are whitelisted? All of the IPs listed here:

    https://whois.arin.net/rest/org/AUTOM-93/nets.

    I’d also recommend you, to stay on the safe side, to update your PHP to the latest version. Your host can assist with it, and we also do have a reference link for you: https://docs.woocommerce.com/document/how-to-update-your-php-version/

    Let me know how you get on!

    Thread Starter bluedrag

    (@bluedrag)

    Hi, sorry for the delayed response here. I will check to see if *.wordpress.com is whitelisted, I will let you know though, out of 6 WordPress websites all hosted on the same server, this is the only website Jetpack is timing out on.

    Since I posted this I have set up a redirect from the http site to the https site.

    • This reply was modified 6 years, 10 months ago by bluedrag.
    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Since I posted this I have set up a redirect from the http site to the https site.

    That’s interesting! I am running the site again in our debugger tool and I got a curl28 error, which happens when there are servers hiccup. Your site is, in fact, having trouble getting online as it’s taking too long to respond and returning an error page.

    Could you double check that again with your host? I suspect the HTTPS redirect you set up might be the culprit this time ??

    Keep me posted!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘The Jetpack server was unable to communicate with your site.’ is closed to new replies.