The error occurs because Google for WooCommerce requires a connection to WordPress.com or Jetpack to function properly. Please follow the setup instructions provided here: https://jetpack.com/support/getting-started-with-jetpack/, install and configure Jetpack, and then try the process again.
I understand your Jetpack is already connected. If not already tried, I suggest disconnecting and reconnecting it. Sometimes, connection issues can resolved like this.
If the issue persists, go to example.com/wp-admin/admin.php?page=connection-test-admin-page (replace example.com with your domain) and share a screenshot of the page with me. You may use https://snipboard.io to upload images and share links here.
Thank you for sharing the screenshots. I reviewed your initial request again. Just to clarify, did you click “Approve” in the error message shown in the screenshot? If so, what happened after you did?
I’m referring to the screenshot below:
Yes, your Jetpack is connected, but it looks like Google for WooCommerce has lost its connection and is requesting approval. Please click “Approve” to grant permission.
Also, I would like to continue using Disable XML-RPC-API plugin, would it be possible just add necessary ip to whitelist? Can you let my know which ip I need to whitelist if so
I tried accessing https://www.shop.handmadehome.me/xmlrpc.php, but it appears to be unreachable, which suggests that XML-RPC is disabled or unreachable. Please enable it and try the process again.
To further troubleshoot the issue, first, check your WordPress Address (URL) and Site Address (URL) under WordPress Admin > Settings > General to ensure they are both set to HTTPS instead of HTTP. Incorrect settings can cause authentication issues and prevent connections from being established properly.
Next, inspect your .htaccess file for any conflicting redirect rules. Multiple redirect rules can interfere with proper site behavior. A correct redirect rule should look like this:
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
If needed, reset your .htaccess file to WordPress’s default version to ensure it is not causing the issue. The default .htaccess file should be:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
Lastly, clearing your site, browser, and server cache can help resolve potential conflicts. Cached data might be preventing recent changes from taking effect, so make sure to clear all caches before retrying the process.
<?php /** * XML-RPC protocol support for WordPress * * @package WordPress */
/** * Whether this is an XML-RPC Request. * * @var bool */ define( 'XMLRPC_REQUEST', true );
// Discard unneeded cookies sent by some browser-embedded clients. $_COOKIE = array();
// $HTTP_RAW_POST_DATA was deprecated in PHP 5.6 and removed in PHP 7.0. // phpcs:disable PHPCompatibility.Variables.RemovedPredefinedGlobalVariables.http_raw_post_dataDeprecatedRemoved if ( ! isset( $HTTP_RAW_POST_DATA ) ) { $HTTP_RAW_POST_DATA = file_get_contents( 'php://input' ); }
// Fix for mozBlog and other cases where '<?xml' isn't on the very first line. if ( isset( $HTTP_RAW_POST_DATA ) ) { $HTTP_RAW_POST_DATA = trim( $HTTP_RAW_POST_DATA ); } // phpcs:enable
/** Include the bootstrap for setting up WordPress environment */ require_once __DIR__ . '/wp-load.php';
/** * Posts submitted via the XML-RPC interface get that title * * @name post_default_title * @var string */ $post_default_title = '';
/** * Filters the class used for handling XML-RPC requests. * * @since 3.1.0 * * @param string $class The name of the XML-RPC server class. */ $wp_xmlrpc_server_class = apply_filters( 'wp_xmlrpc_server_class', 'wp_xmlrpc_server' ); $wp_xmlrpc_server = new $wp_xmlrpc_server_class();
// Fire off the request. $wp_xmlrpc_server->serve_request();
exit;
/** * logIO() - Writes logging info to a file. * * @since 1.2.0 * @deprecated 3.4.0 Use error_log() * @see error_log() * * @global int|bool $xmlrpc_logging Whether to enable XML-RPC logging. * * @param string $io Whether input or output. * @param string $msg Information describing logging reason. */ function logIO( $io, $msg ) { _deprecated_function( __FUNCTION__, '3.4.0', 'error_log()' ); if ( ! empty( $GLOBALS['xmlrpc_logging'] ) ) { error_log( $io . ' - ' . $msg ); } }
Thank you for your response. To further investigate the issue, please go to WooCommerce > Status > Logs and check for any fatal error messages or logs related to Google for WooCommerce. Once found, share the log using https://gist.github.com.
Additionally, navigate to the System Status tab, click Get System Report, then select Copy for Support, and share that report as well.
I checked your site again and found that https://www.shop.handmadehome.me/xmlrpc.php is still inaccessible. This page should display the message: “XML-RPC server accepts POST requests only.”
To troubleshoot, try disabling the MalCare WordPress Security plugin and check if the issue is resolved. If not, look for other security settings or firewalls that might be blocking connection requests. You can also contact your hosting provider to check for any server-side firewalls.
