XML-RPC is Disabled but Jetpack Stopped Working

Does Jetpack Need XML-RPC?

Modern Jetpack versions (9.0+) primarily use the WordPress REST API and OAuth authentication. However, older installations or specific Jetpack features (particularly publicise and some sync operations) may fall back to XML-RPC. If Jetpack breaks after disabling XML-RPC, follow the steps below.

Other Plugins That May Need XML-RPC

• Jetpack (older versions or specific modules)
• WordPress iOS/Android mobile apps (fully REST API now — XML-RPC not needed)
• Some backup plugins (UpdraftPlus, BackupBuddy — check their docs for REST API alternatives)
• Remote publishing clients built before 2018
• Some WooCommerce payment gateways (rare — check with your gateway provider)

Option 1: Re-enable XML-RPC Fully

1. Go to Tools → WP 1 Click LockDown.
2. In the Hardening section, uncheck "Disable XML-RPC".
3. Click Save All Settings.
4. Test your plugin or service.

Option 2: Selectively Allow Jetpack via a Code Snippet

Add this snippet to your theme's functions.php or a site-specific plugin to allow Jetpack's XML-RPC while keeping everything else blocked:

add_filter( 'xmlrpc_methods', function( $methods ) {
    // Keep only Jetpack's required methods
    $allowed = [
        'jetpack.verifyRegistration',
        'jetpack.remoteRegister',
        'jetpack.syncObject',
    ];
    return array_intersect_key( $methods, array_flip( $allowed ) );
} );

Diagnosing Which Plugin Needs XML-RPC

1. Temporarily re-enable XML-RPC in WP 1 Click LockDown.
2. Test whether the broken functionality returns.
3. If yes, identify the plugin causing the dependency by deactivating plugins one by one.
4. Check that plugin's documentation for a REST API alternative or whitelist approach.