• Resolved dm4n

    (@dm4n)


    Hi,

    FYI for people using JetPack with NinjaFirewall – was getting error msg that Jetpack was unable to access my site and display Plugin information after activating NinjaFirewall – tested by deactivating NF and functionality of JP was restored.

    The problem was NF limits access by default to the xmlrpc.php file – to change this go to WP Dashboard > NinjaFirewall > Firewall Policies > WordPress > WordPress XML-RPC API and uncheck the box ‘Block only system.multicall method (default)’

    Voila! JP Plugin function restored.

    Afterwards I also tested WP Dashboard > NinjaFirewall > Login Protection and checked the box for xmlrpc.php and JP continues to work.

    Thanks to the devs for your work!

    https://wordpress.org/plugins/ninjafirewall/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author nintechnet

    (@nintechnet)

    Hi

    I think we’ll add a warning next to the ‘Block only system.multicall method’ option if JetPack is enabled.

    Hi, is there a way to limit allowance for system.multicall to JetPack only and not allow it globally as suggested from dm4n?

    Plugin Author nintechnet

    (@nintechnet)

    Hi

    You can whitelist the xmlrpc.php script and the caller’s IP with the .htninja user configuration file. For instance:

    <?php
    /*
     +===================================================================+
     | NinjaFirewall optional configuration file                         |
     |                                                                   |
     | See: http://nintechnet.com/ninjafirewall/wp-edition/help/?htninja |
     +===================================================================+
    */
    
    if ( strpos( $_SERVER['SCRIPT_FILENAME'], '/xmlrpc.php') !== FALSE && $_SERVER["REMOTE_ADDR"] == 'x.x.x.x' ) {
       return 'ALLOW'; // whitelist
    }

    Replace ‘x.x.x.x’ with the right IP.

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

The topic ‘JetPack and NinjaFirewall’ is closed to new replies.