Backend unreachable. Check NSG, firewall, or port.

Sachin B Nevare 20 Reputation points
2025-11-13T07:41:19.85+00:00
t (Backend setting) Protocol Status Details
10.10.2.4 (appGatewayBackendPool) 8443 (HTTPS) Https Healthy Success
-------- -------- -------- -------- --------
10.10.2.4 (appGatewayBackendPool) 8443 (HTTPS) Https Healthy Success
10.10.2.4 (appGatewayBackendPool) 443 (httpsgatewaysettings) Https Unhealthy Received invalid status code 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. To learn more visit - https://aka.ms/StatusCodeMismatch.|
10.10.2.5 (DEVBEPool) 8080 (httpdev8080) Http Unhealthy Cannot connect to backend server. Check whether any NSG/UDR/Firewall is blocking access to the server. Check if application is running on correct port. To learn more visit - https://aka.ms/servernotreachable.|
10.10.2.5 (DEVBEPool) 8081 (http8081dev) Http Healthy Success
10.10.2.5 (DEVBEPool) 443 (https443dev) Https Healthy Success
Azure Application Gateway
Azure Application Gateway
An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.
0 comments No comments
{count} votes

Answer accepted by question author
  1. Q&A Assist
    2025-11-13T07:41:40.5666667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error messages indicate issues with the backend health of your Azure Application Gateway. Here are the key points to consider based on the provided details:

    1. Status Code Mismatch: For the backend server at 10.10.2.4 on port 443, the health probe is receiving an invalid status code. The probe is configured to accept status codes in the range of 200-399, but it is not receiving a valid response. You may need to either modify the probe configuration to accept the current response or resolve the underlying issues with the backend application to ensure it returns a valid status code.
    2. Backend Connectivity Issues: For the backend server at 10.10.2.5 on port 8080, the health probe is unable to connect. This could be due to network security group (NSG) rules, user-defined routes (UDR), or firewall settings blocking access. Ensure that the application is running on the correct port and that the necessary inbound rules are configured in the NSG to allow traffic.

    To troubleshoot further, consider the following steps:

    • Check the NSG rules associated with the Application Gateway and the backend servers to ensure that they allow the necessary traffic.
    • Verify that the application on the backend servers is running and listening on the expected ports.
    • Review any UDRs that might be misrouting traffic away from the backend servers.

    By addressing these points, you should be able to resolve the backend connectivity issues and ensure that your Application Gateway can successfully probe the backend servers.


    References:

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.