xmlrpc connection error

  • Resolved peterjameswass

    (@peterjameswass)


    1 week, 4 days ago

    Jetpack was reporting that WordPress.com requests to xmlrpc.php were blocked with HTTP 403.

    Our host, 20i, adjusted its security configuration and has confirmed from HAProxy logs that repeated Jetpack XML-RPC requests and wordpress.com connection/test-wpcom requests now return HTTP 200, with no 403 responses. Cloudflare is also not blocking or challenging these requests.

    We disconnected the complete Jetpack site connection and successfully reconnected it using the same WordPress.com account. The Jetpack warning banner then disappeared, but WordPress Site Health still reports the previous 403 connection error.

    The official Jetpack Debug Tool continues to return only “Unknown error”, including after the successful reconnection.

    Site URL: https://colliercatchpole.co.uk

    Could you check the WordPress.com side of the connection and identify why the Debug Tool and Site Health test are still failing despite the successful connection and HTTP 200 responses?

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Alin (a11n)

    (@alinclamba)

    1 week, 3 days ago

    Hi @peterjameswass,

    Thanks for the detailed write-up, it helped track this down quickly.

    Your Jetpack site connection itself is fine. The issue is that Cloudflare is blocking the requests before they reach your server.

    When we checked from our end, the response came back with the header Cf-Mitigated: challenge, meaning Cloudflare is serving a JavaScript challenge to automated requests, including Jetpack’s. Since Jetpack’s servers can’t solve a browser-based challenge, Cloudflare returns 403 Forbidden and the request never reaches 20i’s HAProxy.

    That’s why 20i correctly sees HTTP 200 in their logs (only browser traffic that already passed Cloudflare gets there), and why the Debug Tool, Site Health, and the admin banner keep failing.

    To resolve this, you’ll need to configure Cloudflare to allow Jetpack’s requests through without a challenge. These two guides should help:

    Once you’ve made the changes, let us know here and we can verify the connection from our side.

    Thread Starter peterjameswass

    (@peterjameswass)

    1 week, 3 days ago

    Thanks Alin.

    I’ve deployed a new Cloudflare rule and the issue (at least on the Site Health page and Jetpack Debug page) seems to have been resolved.

    Really appreciate your help.

    All the best,

    Peter

    Plugin Support Alin (a11n)

    (@alinclamba)

    1 week, 3 days ago

    Glad to hear that fixed it, Peter! Thanks for confirming.

    If you have a moment, we’d really appreciate it if you’d consider leaving a review for Jetpack here: https://wordpress.org/support/plugin/jetpack/reviews/

    All the best!

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.