Hi Web1776,
Sebastian here, I hope you are doing well. Thanks for the detailed report, and for already ruling out the obvious stuff by testing xmlrpc.php directly and checking with WP Engine.
I dug into the connection for apslaw.com and found the actual cause. On our side, the site’s registered URL was pointing to an internal WP Engine environment address rather than your live production domain. That internal address isn’t meant for public or API traffic, which is why WordPress.com’s daily connection check (and the xmlrpc.php request it makes) kept getting blocked, even though your manual test on the live site worked fine. I’ve corrected that on our end, and the connection is noticeably healthier now.
There’s one more step to fully finish this off, and it does need action on your side. Right now, your site has what’s called a “site-only” connection, meaning no WordPress.com account is linked as the connection owner yet. Several Jetpack features, including the one behind this Site Health notice, need a connected account to work properly. To fix that:
- Go to the Jetpack menu in your WP Admin dashboard.
- Scroll down to the Connections area.
- Click “Connect your WordPress.com account” to link Jetpack to your WordPress.com account.
More on why this matters here:
https://jetpack.com/support/why-the-wordpress-com-connection-is-important-for-jetpack/
Once that’s done, the Site Health notice should clear on its own. Let us know if you run into anything or if it doesn’t resolve after connecting the account, and we can take another look.
Warm regards,
