Jetpack Connection Health Warning

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    6 days, 4 hours ago

    Hi @mcarter76!

    Thanks for following up and for sharing the forum thread.

    We understand that you’re still seeing the same warning with WooCommerce Tax 3.7.0 installed. The warning is generated by the WordPress.com connection health check included with the bundled Jetpack Connection package, rather than by the WooCommerce Tax calculation service itself.

    The connection check periodically attempts to reach your site through /xmlrpc.php. If incoming XML-RPC requests are blocked by your firewall or hosting configuration, the request returns a 403 and the connection package reports the xmlrpc_request_blocked condition. This can occur even when WooCommerce Tax’s outgoing tax requests are working normally.

    At this point, the available options are:

    1. Allowlist WordPress.com/Jetpack IP ranges for /xmlrpc.php while keeping XML-RPC blocked for other incoming requests. Jetpack documents the IP ranges here: Jetpack IP allowlisting documentation
    2. Keep XML-RPC blocked and suppress the connection error notice using the documented Jetpack Connection filter:
    add_filter( 'jetpack_connection_error_notice_message', '__return_empty_string' );

    This suppresses the admin notice but does not make the Site Health connection test pass.

    We have also shared the concern about the warning’s severity and messaging with the developers, since the XML-RPC check is separate from the outgoing WooCommerce Tax requests.

    If you’re still seeing the warning after updating to 3.7.0, that is consistent with the current connection-check behavior when /xmlrpc.php remains blocked.

    Thread Starter Mike Carter

    (@mcarter76)

    5 days, 23 hours ago

    Hi Shazeen,

    Thanks for the workaround. I can definitely add that filter to functions.php in the meantime.

    Small correction: IXR_Server returns a 405 Not Allowed response, not a 403.

    I’m unsure of the last time the jetpack connection health check produced a positive result, but I do know that xmlrpc.php is unblocked. I’ve tested this by observing my web server logs. Automattic’s APN and IP’s have both been whitelisted in Cloudflare’s WAF, and I can see the Jetpack request being handled by Apache and PHP FPM directly. The 405 response is definitely coming from IXR_Server in the corresponding WordPess library and not from Cloudflare.

    Do you have systems where this test is running correctly and xmlrpc.php is unblocked?

    Thanks,
    Mike

    • This reply was modified 5 days, 23 hours ago by Mike Carter.
    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    4 days, 9 hours ago

    Hi @mcarter76!

    Thank you for sharing the additional information and for checking the server logs. That’s helpful.

    I have a test site where I’m not seeing the same notice, so I’d like to gather some additional details from your site to investigate this further.

    Could you please share the System Status Report from WooCommerce → Status → System Status? You can paste it on Pastebin and enable the Burn After Reading option for privacy. Please also share your website URL.

    Thank you for your help!

    Thread Starter Mike Carter

    (@mcarter76)

    3 days, 23 hours ago

    Here is the status report:

    https://pastebin.com/zujddfLQ

    Connection Error Warning (Displayed in Site Health):

    A healthy Jetpack Connection allows connected plugins (such as Jetpack and WooCommerce) to provide features like Stats, Site Security, and Payments.

    Error WordPress.com reached your site but the request was blocked (HTTP 405). This is usually caused by a firewall, security plugin, or server rule rejecting requests from WordPress.com.

    Ask your host or security provider to allow requests from WordPress.com to your site’s xmlrpc.php file. Reconnecting will not resolve this. If you need further help, contact Jetpack support.

    Please contact Jetpack support. (opens in a new tab)

    Thread Starter Mike Carter

    (@mcarter76)

    23 hours, 33 minutes ago

    Any update on this? Were you able to view the status report?

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    3 hours, 23 minutes ago

    Hi @mcarter76!

    Thanks for sharing the System Status report. I’ve reviewed it, and everything appears to be configured correctly from the WooCommerce side.

    I also checked your site and can confirm that requests to xmlrpc.php are working correctly when accessed directly. However, I noticed that Cloudflare presents a security check when accessing the site. This makes me suspect that a Cloudflare security rule or challenge may be interfering with requests from WordPress.com/Jetpack.

    Could you please contact your hosting provider and ask them to check whether anything on their server or security layer is blocking or modifying requests from WordPress.com/Jetpack?

    Also, if you have access to Cloudflare, please check the Security Events logs for any blocked or challenged requests to xmlrpc.php, particularly requests originating from WordPress.com/Jetpack. If you find any such requests, please allow them or adjust the relevant Cloudflare security rule.

    Once you’ve checked this with your host/Cloudflare, please let us know what you find and we’ll be happy to investigate further.

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

You must be logged in to reply to this topic.