Skip to main content

Troubleshooting (hardware-based WAFs)

This page relates to hardware-based WAFs only.

Typically WAFs suffer from very few problems as long as they have been set up correctly.

Here are a few possible fixes in the event of any issues:

  • WAF doesn't appear to be working: Ensure the DNS is pointing towards the WAF IP rather than your internal server IP, as the WAF is acting as a proxy to provide the smoothest way of checking incoming traffic.

  • WAF isn't blocking any traffic: This is most likely due to the WAF being in learning mode. Contact ANS immediately to have the WAF fully switched-on.

  • 400 error: This is typically due to either the WAF having a problem connecting to your internal server, or a problem on the internal server itself.

  • 500 error: This isn't typically a WAF problem, usually it means a problem has occurred server-side

If you experience any problems with your WAF then please contact support or raise a ticket via ANS Glass.