Request time-out or connectivity issues with user requests.None of the VMs or instances in virtual machine scale set are healthy.Azure Application Gateway's backend pool isn't configured or empty.Invalid or improper configuration of custom health probes.Backend VMs or instances of virtual machine scale set aren't responding to the default health probe.NSG, UDR, or Custom DNS is blocking access to backend pool members.This error may happen for the following main reasons: OverviewĪfter you configure an application gateway, one of the errors that you may see is Server Error: 502 - Web server received an invalid response while acting as a gateway or proxy server. To learn how to migrate to the Az PowerShell module, see Migrate Azure PowerShell from AzureRM to Az.
See Install Azure PowerShell to get started. We recommend that you use the Azure Az PowerShell module to interact with Azure.
0 kommentar(er)
