The WAF 2.0 module is able to block web-based attacks before they could reach the server. If a well-aimed web-based attack like a PHP code injection reaches the server it will cause serious issues on the server.
Also, the most popular CMS-es and their plugins, like WordPress or Drupal have a...
If the pre-requirements are met but the WAF module is still not running we will need to check a few things.
Connections from localhost
The web server has to accept connections from 127.0.0.1 to http://<server_IP>:80 and to https://<server_IP>:443 in order for the WAF module to...
In Plesk, the X-Forwarded-For header is already included with all IP addresses of the server in the configuration files of all web server applications. If remoteip is not enabled yet, you need to enable remoteip. from Plesk.
Go to Tools and settingsApache Web ServerTick in remoteip’s checkbox ...
If you are using cPanel/WHM please make sure to open/allow the 60418 port on TCP on your server and on the firewall in front of it (if there is one). It is required for the CaptchaHTTPS service.
This header needs to be set up in your web server used to serve your domains.
Please insert you...
Disable the Transparent mode in the WAF module
As of BitNinja version 2.29.5, the default redirection mode in the WAF module is the transparent mode. So if you wish to use the X-Forwarded-For header in your web server you will need to disable the transparent mode in the WAF module's config fil...
First, we need to check what kind of error code you see.
Error 502
If you see this screen when you try to access a domain that is behind CloudFlare while BitNinja is running with the WAF module enabled and the Trusted proxy module enabled.
Issue bitninjacli --module=SslTerminat...
By default, WAF 2.0 will only create port redirections for public IPs. However, it can be set to observe on the private interface. It can happen, that your server does not have a public interface, in this case, there are more possibilities
If there is a gateway in front of the server, whic...
Some applications miss behave behind a proxy. This is why we need to force a redirection to remain https most of the time.
Solution
This behavior can be changed:You just need to change this line highlighted in the picture:
Run these commands as a root user in your server’s terminal t...
Apache
Open your Apache configuration file with your favourite text editor. Insert the following lines at the end of the httpd.conf or apache2.conf file. On Debian you can find the configuration file usually at /etc/apache2/httpd.conf or at /etc/apache2/apache2.conf The loc...
If you do not use any kind of CDN service, then there is no need to enable Trusted Proxies module, Transparent proxy is sufficient for WAF 2.0 to work properly.
To enable this feature you will need to edit the WafManager’s config file which you can find here: /etc/bitninja/WAFManager/...
