403 error even after allowing IP in network restriction

kalyan reddy 181 Reputation points

A bit of information regarding my setup.

I have a web app, which I have been using for the past couple of years. I use the application gateway's frontend Ip configuration to access my web app. For this, I added the frontend IP address to the network restriction rules of my web app. It has been working fine. since today morning, I keep getting an error on the application gateway saying that the backend is unhealthy with the following error message

"Received invalid status code: 403 in the backend server’s HTTP response. As per the health probe configuration, 200-399 is the acceptable status code. Either modify probe configuration or resolve backend issues"

After some research, I found that I can use the "Diagnose and solve problems"(Which client IPs got rejected due to IP restriction?) option in the web app to find out which requests from which IP addresses have been blocked.

In the logs i see that ipv6 addresses like "fde2:8daa:2000:f05a:6a20:100:a88:f306"(not the exact one). But, i have put ipv4 address of frontend of app gateway.

This started happening today morning. Please help me out

Azure Application Gateway
Azure Application Gateway
An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.
788 questions
Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
5,643 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Serhiy Hryhorchuk 1 Reputation point

    Did you resolve this issue?
    I have the same error for no reason.