No Longer Identifies xmlrpc.php Location (Site home page different than WP dir)
-
I temporarily disabled Jetpack a few weeks back to see if it conflicted with a different plugin on WordPress 6.3.1, unfortunately when I turned it back on, the site connection was lost.
I just spent weeks rechecking Cloudflare (DNS nameserver), QUIC.cloud (DDoS & CDN), & cPanel (.htaccess & wp-config.php) to whitelist all IP ranges plus some other configuration recommendations I found searching the web.
After using this tool, https://jptools.wordpress.com/debug/, the report told me Jetpack could not communicate with my xmlrpc.php file on the root directory & that I should try navigating to the file directly in my web browser.
My WordPress installation is self-hosted on a subdirectory folder named “/wordpress/” so obviously the xmlrpc.php would not be accessible from the root domain [i.e. https://www.example.com] (see https://www.ads-software.com/documentation/article/giving-wordpress-its-own-directory/.
I navigated towards “www.example.com/wordpress/xmlrpc.php” & got a response of “XML-RPC server accepts POST requests only.” so no issues there…
I highly doubted that Jetpack developers could overlook such a common scenario but I still decided to temporarily change my Site Address (URL) to match my WordPress Address (URL).
Wow would you look at that? Now attempting to connect Jetpack miraculously works! After you can go ahead & change the Site Address (URL) back to the root domain.
I’ve never had this issue in the 12+ years of using Jetpack since v1.0 but I hope this post saves many people unnecessary headache & time wasted.
TL;DR: If your Site Address (URL) & WordPress Address (URL) are different, you are not going to be able to finalize setup because currently Jetpack looks for the xmlrpc.php file at the Site Address (URL).
- The topic ‘No Longer Identifies xmlrpc.php Location (Site home page different than WP dir)’ is closed to new replies.