Full WAF not working

  • Hi there,

I try to activate the Full WAF but always get the info "Oops! Full WAF mode is not enabled yet. Because PHP caches INI files, you may need to wait up to five minutes before the changes are reloaded by the PHP interpreter. "

I’ve tried Apache CGI/FastCGI with .user.ini (waiting 5 minutes) and Apache CGI/FastCGI with php.ini – no luck; I also tried to edit the .htacess

My hoster is goneo...

Here is what the troubleshoot says:

HTTP server: Apache/2.4.57 (Debian)
PHP version: 8.1.21
PHP SAPI: FPM-FCGI

auto_prepend_file: /web/1/000/051/661/xxxxxxx/htdocs/xxxxxx/wp-content/nfwlog/ninjafirewall.php
Loader's path to firewall: /data/web/1/000/051/661/xxxxxx/htdocs/xxxxxx/wp-content/plugins/ninjafirewall/lib/firewall.php
wp-config.php: found in /data/web/1/000/051/661/xxxxxx/htdocs/xxxxxx/wp-config.php
NinjaFirewall detection: NinjaFirewall WP Edition is loaded (Full WAF mode)

Loaded INI file: /etc/php/8.1/fpm/php.ini
user_ini.filename:.user.ini
user_ini.cache_ttl:300 seconds
User PHP INI: .user.ini found -

DOCUMENT_ROOT: /web/1/000/051/661/xxxxxx/htdocs/xxxxxx
SCRIPT_FILENAME: Warning: there's a double slash (//) in the SCRIPT_FILENAME variable: //web/1/000/051/661/xxxxxx/htdocs/xxxxxx/troubleshoot.php
This may prevent PHP from loading its INI files.
ABSPATH: /data/web/1/000/051/661/xxxxxx/htdocs/xxxxxx/ (ABSPATH != DOCUMENT_ROOT)
WordPress version : 6.3.1
WP_CONTENT_DIR: /data/web/1/000/051/661/xxxxxx/htdocs/xxxxxx/wp-content
Plugins directory: /data/web/1/000/051/661/xxxxxx/htdocs/xxxxxx/wp-content/plugins
User Role:Administrator
User Capabilities: manage_options: OK - unfiltered_html: OK
Log dir permissions: /data/web/1/000/051/661/xxxxxx/htdocs/xxxxxx/wp-content/nfwlog dir is writable
Cache dir permissions:/data/web/1/000/051/661/xxxxxx/htdocs/cellulite/xxxxxx/nfwlog/cache dir is writable
    • This topic was modified 1 year, 2 months ago by maxidavis.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author nintechnet

    (@nintechnet)

    You’re running FPM-FCGI, you need a .user.ini file, not a php.ini.
    The troubleshooter script returns that it is loaded:

    NinjaFirewall detection: NinjaFirewall WP Edition is loaded (Full WAF mode)

    If the NinjaFirewall dashboard says it isn’t, that means your INI doesn’t apply recursively, i.e. it has no effect inside a subfolder, but only in the main web root folder. That’s why the script detects it (you uploaded it inside the web root folder), but not the plugin (it’s located inside subfolders – /wp-content/plugins/). You would need to ask your hosting company about that because, normally, the .user.ini applies recursively.

    Additionally, there’s seems to be an issue with your PHP FPM configuration:

    SCRIPT_FILENAME: Warning: there’s a double slash (//) in the SCRIPT_FILENAME variable: //web/1/000/051/661/xxxxxx/htdocs/xxxxxx/troubleshoot.php

    I’m not sure if that is the reason why it breaks the firewall, but I recommend that you fix your PHP FPM configuration so that SCRIPT_FILENAME doesn’t have a double leading ‘/’ character.

    Thread Starter maxidavis

    (@maxidavis)

    Thanks for the answer. I created the .user.ini file but the issue persists.

    How can I change the PHP FPM configuration?

    Plugin Author nintechnet

    (@nintechnet)

    You would need to ask your host about how to make the .user.ini script recursive. That would allow the Full WAF mode to work.

    Regarding the SCRIPT_FILENAME environment variable, maybe check Apache’s main configuration file ( /etc/apache2/apache2.conf) and the vhost configuration files in /etc/apache2/sites-available/. Did you configure that server yourself? There may be a double slash somewhere (in the document root for instance).

    Thread Starter maxidavis

    (@maxidavis)

    Okay, so all issues can only be solved by the hoster. I contacted them and hope they can fix it. please leave this case open

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Full WAF not working’ is closed to new replies.

Tags