Support » Plugin: NinjaFirewall (WP Edition) - Advanced Security » v4.* installations on shared servers child sites

  • Resolved muggz

    (@muggz)


    I have NF installed in Full WAF mode on a parent site at the virtual root level /*/public_html/

    Installing to a child site located at /*/public_html/child1/ installs without error but finds and uses the parents auto_prepend_file and child1’s overview page instantly reports that it’s running in Full WAF mode. No changes are made to */child1/php.ini or */child1/.htaccess and NF on the child site runs with limited functionality.

    Temporarily deactivating the parent install and commenting out its auto_prepend_file= line in /*/public_html/php.ini allows for a proper installation on the child sites.

    This behavior is apparent in v4.0 and v4.01 and was not an issue in v3.x.x. Upgrading child sites from v3.x.x or v4.0 to the latest version do upgrade without issues.

    Thank you for the awesome tool.

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

    (@nintechnet)

    It is the normal behavior. The problem was that version 3.x didn’t detect another loaded firewall, and that was a mistake, The new one detect it. In the next release, it will warn the user and remind them that they need to disable the firewall in the parent folder in order to install a new one in a subfolder.

    Thank you, that should help to avoid a false sense of security that currently exists with multiple installs on shared servers.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.