Skip to content

Issues During NGINX Wallarm Ingress controller Installation

This troubleshooting guide lists common issues you can face during the Wallarm NGINX-based Ingress controller deployment. If you did not find relevant details here, please contact Wallarm technical support.

How to check which clients' IP addresses are detected/used by the Ingress controller?

  • Take a look at the controller container’s log and find records about handled requests. In the default logging format the first reported field is the detected client IP address. 25.229.38.234 is the detected IP address in the example below:

    [wallarm-ingress-nginx-ingress-controller-775cf75564-6jlt9 nginx-ingress-controller] 25.229.38.234 - - [14/Mar/2020:23:55:11 +0000] "GET /ping HTTP/1.1" 200 893 "-" "curl/7.64.1" 172 0.020 [default-sise-80] [] 172.17.0.5:8080 893 0.020 200 d8402076753798d3b065269c16d4b34f

  • Go to your Wallarm Console for the US cloud or for the EU cloud → the Attacks section and expand request details. An IP address is displayed in the Source field. For example:

    IP address from which the request was sent

    If the list of attacks is empty, you can send a test attack to the application protected by the Wallarm Ingress controller.

How to check that the Ingress controller is receiving the X-FORWARDED-FOR request header?

Please go to Wallarm Console for the US cloud or for the EU cloud → the Attacks section and expand the request details. In the displayed request details, pay attention to the X-FORWARDED-FOR header. For example:

The X-FORWARDED-FOR header of the request

If the list of attacks is empty, you can send a test attack to the application protected by the Wallarm Ingress controller.