0

We are using Azure Application Gateway with WAF. We have configured a timeout of 3600 seconds, and we performed the following scenario with Azure WAF and without WAF:

With Azure: The application runs around 1 hour and then shows 504 Error.

And without Azure, the Application got the result within 20 to 30 minutes.

Could you please help with this issue?

Parth Mehta
  • 1
  • 2
  • Could you please share the `backend health status` of the gateway once, so that we can reproduce this scenario? If we get a `504 error`, it could be due to an `unhealthy state`. As per my initial analysis, this issue may be caused by the timeout threshold in the probe settings. Please increase the timeout on health probe and please refer this [link](https://learn.microsoft.com/en-us/azure/application-gateway/application-gateway-backend-health-troubleshooting) – Harshitha Oct 20 '22 at 06:43
  • Thanks for your answer. we have already increased the timeout value and server state is healthy. Our application smoothly works without Azure Application Gateway. – Parth Mehta Oct 21 '22 at 07:03

1 Answers1

0

Either in Azure Application Gateway also we can get good results by doing like this

Update Backend Settings either http / https protocols request time-out to example 3600 sec

enter image description here Create an health probe to test our application is working fine or not

enter image description here

Test the health probe, depends on the output we can figure out the issues. if any firewall block, please allow those ports from NSG.

Swarna Anipindi
  • 792
  • 2
  • 9