Jetpack Communication Error

  • Resolved nerdoflinux

    (@nerdoflinux)


    6 years, 8 months ago

    I recently switched from apache to lighttpd, and Jetpack stopped working. I used the same rewrite rules, and /xmlrpc.php returns the correct message, and the correct message for /xmlrpc.php?rsd. Running curl -A ‘Jetpack by WordPress.com’ -is -H ‘Content-Type: text/xml’ –data ‘<?xml version=”1.0″?><methodCall><methodName>demo.sayHello</methodName><params></params></methodCall>’ ‘https://gateblogs.com/xmlrpc.php&#8217; && echo

    Returns the following for apache:
    0; path=COOKIEPATH
    Set-Cookie: QnKVvgyjBb=e4x5FOl1S%40; expires=Wed, 28-Mar-2018 15:06:28 GMT; Max-Age=3600; path=COOKIEPATH
    X-LiteSpeed-Cache-Control: no-cache
    Vary: Accept-Encoding
    Expect-CT: max-age=604800, report-uri=”https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct&#8221;
    Server: cloudflare
    CF-RAY: 402aa831dc789248-EWR

    <?xml version=”1.0″ encoding=”UTF-8″?>
    <methodResponse>
    <params>
    <param>
    <value>
    <string>Hello!</string>
    </value>
    </param>
    </params>
    </methodResponse>

    And the following for lighttpd:

    Set-Cookie: __cfduid=d69c6c476e8a8b4104518a882e5da44fc1522249272; expires=Thu, 28-Mar-19 15:01:12 GMT; path=/; domain=.gateblogs.com; HttpOnly; Secure
    Set-Cookie: eFcLBrViasNyQ=0B_%2AIgsJ%404wDp; expires=Wed, 28-Mar-2018 16:01:12 GMT; Max-Age=3600; path=COOKIEPATH
    Set-Cookie: vHaptPuAqNnMzGLW=1OdrwTgqcNxtZ0.%40; expires=Wed, 28-Mar-2018 16:01:12 GMT; Max-Age=3600; path=COOKIEPATH
    Set-Cookie: c_uINfQa=FEsjKuzn; expires=Wed, 28-Mar-2018 16:01:12 GMT; Max-Age=3600; path=COOKIEPATH
    Set-Cookie: QnKVvgyjBb=e4x5FOl1S%40; expires=Wed, 28-Mar-2018 16:01:12 GMT; Max-Age=3600; path=COOKIEPATH
    Expect-CT: max-age=604800, report-uri=”https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct&#8221;
    Server: cloudflare
    CF-RAY: 402af8807d0a9224-EWR

    <?xml version=”1.0″ encoding=”UTF-8″?>
    <methodResponse>
    <params>
    <param>
    <value>
    <string>Hello!</string>
    </value>
    </param>
    </params>
    </methodResponse>

    But the Jetpack debugger gives a communication error. It was working fine with apache, so I know it’s not a problem with any of my plugins. I also know it’s not a dependency issue because it returns the correct output for cURL

    • This topic was modified 6 years, 8 months ago by nerdoflinux.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    the Jetpack debugger gives a communication error

    Can you please send us those results privately, so we can take a closer look?

    1. Go to the Jetpack page in your dashboard.
    2. Click on the Debug link appearing at the bottom of the page.
    3. Click the link that says “click here to contact Jetpack support.”
    4. Fill in the description box and your name and email address.
    5. Click the “Contact Support” button to send us the debug results privately. It’s best not to post this information on public forums, as it contains private details about your site.

    Thanks!

    Thread Starter nerdoflinux

    (@nerdoflinux)

    I did that, and I didn’t get even an automated reply and its been over 24 hours.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    That’s odd that you didn’t get an automated reply. Maybe try to copy all those debug results and paste them into this contact form instead?
    https://jetpack.com/contact-support/?rel=support

    Thank you!

    Thread Starter nerdoflinux

    (@nerdoflinux)

    I did that, twice, and didn’t get any response, automated or not.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    I looked through our database and could not find any email from the email address linked to your WordPress.com account. I also could not find a ticket mentioning your site URL, gateblogs.com.

    Could you try to contact us once again?

    Thank you.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Jetpack Communication Error’ is closed to new replies.

Tags