• Resolved danedigi

    (@danedigi)


    Recently moved this site over to Pantheon for hosting, and cannot connect to jetpack fully. I had to enable xml-rpc because it is disabled by default. According the pantheon docs “Pantheon does not support XML-RPC if it is enabled. You must resolve any issues you experience from enabling XMLPRC on your own.” So the support ticket I opened with them will likely go nowhere. Site is connected in wp-admin but get error message in the Jetpack Debug Tool and WordPress.com account settings.

    Debug error:
    Communication error
    We were unable to make an XML-RPC request to your website. Please make sure that XML-RPC is turned on and that Jetpack is installed, activated and connected with your WordPress.com account. If the error persists, try disconnecting and connecting Jetpack again.

    WordPress.com error: The Jetpack site is inaccessible or returned an error: server error. requested method jetpack.jsonAPI does not exist. [-32601]

    I have tried deactivating all plugins, switching themes, reinstalling jetpack, and disconnecting/reconnecting throughout all this and still the same error. My xml-rpc is accessible and the Jetpack namespaces are too.

    Please help thanks!!

    The page I need help with: [log in to see the link]

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

    (@erania-pinnera)

    Hi there, @danedigi,

    I’m sorry to hear about the trouble, but thanks for reaching out.

    When we tested the Jetpack Connection to your site, we saw a 400 Bad Request error. You can read more about the error here.

    To address this, I suggest checking if you have any security plugins that might be blocking our requests. If not, as your initial message seems to suggest, try contacting your hosting provider once again, and asking them to check their security logs to see if they are blocking or otherwise limiting incoming and outgoing connections over XML-RPC.

    Jetpack uses this file to communicate with your site, but some hosts block connection requests to that file. Our requests look like the following:

    – File: https://shop.cornerstonebakery.net/xmlrpc.php
    – User-agent header: Jetpack by WordPress.com
    – IPs: https://jetpack.com/support/how-to-allowlist-jetpack-ip/

    Please ask them to allowlist the IP addresses listed above. If your host confirms that they don’t use the xmlrpc endpoint by default, you can ask them to set it up for you as an exception or to get an alternate endpoint. For the records, I have already tested the connection with an alternate endpoint, and I received the same 400 error – which makes me think that something else is conflicting with Jetpack at the moment.

    Let me know what you find out, and we’ll take it from there if necessary. Thanks!

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hey @danedigi,

    Do you have updates about that, do you still need help? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!

    Thread Starter danedigi

    (@danedigi)

    Hi @erania-pinnera thanks for your response! I did try Pantheon steps to open up the xmlrpc.php endpoint, I tried both leaving open to anyone and tried adding the IP addresses to an allowlist but neither worked. I do have a ticket open with Woo Support and they are trying to help as well.

    I’m using jetpack for the WooCommerce app, so in the meantime i connected the app with store credentials and turned on email notifications to get around this connection issue

    Edit: one more thing, weirdly I was getting push notifications from the woo app about new orders, I just couldn’t do anything else.

    • This reply was modified 4 months ago by danedigi.
    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there, @danedigi,

    Thanks for the follow-up! The connection issue sounds like a mystery that still need to be solved, and we want to help with this.

    Since you’re being supported by our Woo colleagues, this is what I’d recommend you to do:

    • keep working on them
    • mention the Jetpack connection issue to them
    • if they cannot fix that, ask them to re-route your ticket/email to our department onc ethey have figure out the Woo-related issue you’re addressing
    • mention to them also the push notifications from the Woo app about orders, as they are the best skilled people to assess that initially.

    Let me know if that sounds like a good plan! This way, you can keep all the conversations on one thread only via email.

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hello @danedigi,

    Do you have updates about that, do you still need help? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!

    Thread Starter danedigi

    (@danedigi)

    Thanks @erania-pinnera, I’m testing a fix now that I found here: https://blog.coriolis.ch/2015/07/03/using-wordpress-jetpack-with-nginx-and-varnish/
    adding this to wp-config.php: $_SERVER[‘SERVER_PORT’] = 80;

    Woo Support passed me over to Jetpack support and they said it looked like there was an issue with the Varnish cache. I tested the fix and so far everything looks to be working correctly. But I’ve asked Pantheon to make sure this fix wont break anything.

    Hi @danedigi,

    Thanks for the update and letting us know that you were able to fix the issue with Jetpack connection. I checked and on our end too the connection seems to be working correctly.

    Let us know if you have any other issues with the Jetpack connection.

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.