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 work.
Are all IP addresses of the server added to the X-Forwarded-For header?
Have you set up the Transparent Proxy mode in the WAF module instead of the X-Forwarded-For header in your webserver?
The network interface facing the internet has only a Private IP address?
Does your server have multiple network interfaces?
Are the required ports open?
| Protocol | Port | BitNinja module(s) |
|---|
| TCP | 60412 | CaptchaHttp, CaptchaSmtp |
| TCP | 60413, 60418* | CaptchaHttps |
| TCP | 25 | CaptchaSmtp |
| TCP | 60201 | CaptchaSmtp |
| TCP | 60210 | CaptchaFtp (active) |
| TCP | 60211-60250 | CaptchaFtp (passive) |
| TCP | 60300 | WAF HTTP |
| TCP | 60301 | WAF HTTPS |
| TCP | 60414, 60415 | SslTerminating |
| TCP | 60416 | TrustedProxy HTTP |
| TCP | 60417 | TrustedProxy HTTPS |
Is the bitninja-sslt module running?
Are the SSL certs found by the BitNinja cert miner?
Did the IpFilter module have an unsuccessful connection test?
Still not working?
Send a ticket to our Support Ninjas.
