Application Gateway to apache load balancer application is not working

Question

Hi Team,

I have configured my application in AKS level, apache is running on one POD and acts as a load balancer.

Application is running without any issues by apache loadbalancer.

Note:- Apache Load Balancer --> Application Login Page --> Landing Page --> other pages(based upon the click events for ex: user page)

Problem Statement:

If I am accessing the apache load balancer(apache --> application) by application gateway, after landing page again redirected to login page.

Application Gateway --> Apache Load Balancer --> Application Login Page --> Landing Page --> it is redirecting to login page(if click any other pages page)

Expecting Scenarios,

Application Gateway --> Apache Load Balancer --> Application Login Page --> Landing Page --> other pages(based upon the click events for ex: user page)

Answer 1

Hello Thayumanaswamy, Naresh, Welcome to microsoft Q&A, Thankyou for posting your query here. 1.Make sure that the session persistence settings in the application gateway are configured correctly and set to the same value as in the Apache load balancer. 2.Check the backend health of the Apache load balancer in the application gateway. Ensure that the backend health is healthy and there are no errors i.To check the backend health of the Apache load balancer, you can use the Azure portal or Azure CLI. ii. In the Azure portal, navigate to the Application Gateway resource and select the Backend health option under the Monitoring section. iii. This will show you the health status of all the backend servers in the backend pool. iv. If the backend health is not healthy, you can check the logs in the Apache load balancer to see if there are any errors or issues that might be causing the problem. v. You can also check the network security group (NSG) rules and user-defined routes (UDRs) to make sure that they are not blocking access to the backend pool members. 3.Check the session persistence settings in the application gateway. Make sure that the session persistence is configured correctly and is set to the same value as in the Apache load balancer. 4.Confirm the backend pool settings in the application gateway are configured correctly and pointing to the correct backend servers. 5.Ensure that the listener settings in the application gateway are configured correctly and listening on the correct port. 6.Verify the HTTP settings in the application gateway to ensure they are configured correctly and set to the same value as in the Apache load balancer. i. Make sure that the HTTP settings are configured correctly and are set to the same value as in the Apache load balancer. ii.If the HTTP settings are not configured correctly, the application gateway might not be able to communicate with the backend servers, which can cause the issue. Hope this helps you.