Skip to main content

What to do when I receive 502 error code on an Azure endpoint - HTTP Request failed. Error Code: 502.

By
From time to time we started to receive from Azure Web 502 HTTP error code during some load tests. In this post we will talk a little about what can be the root cause of this error and how we can manage it.
HTTP client exception: HTTP Request failed. Error Code: 502.
This error does not appears very often, but can be annoying. Especially because the root cause of this error cannot be traced easily.
When you have an Azure WebApp (Azure WebSite) or an Azure Web Role this error is not returned by your application. This error is returned in most cases by Azure Load Balancer that plays the role of ARR (Application Request Routing).
When ARR doesn't receive a response from your application in 3 minutes (default timeout for Azure WebApp), a 502 error is returned. For ARR this means that the system is not in a good health, it could be even in a Pending state. The 3 minutes timeout period is specific for Azure Web App (Azure Web Sites)
Solutions
First think that you need to do is to look into your system and try to identify what part of the system is so slow or what trigger a crash into your system.

The second question that you should ask yourself is if is normal and acceptable from your side to have a request that takes more than 3 minutes.

  • If no, than you should try to see how you can optimize your system to reduce the timeout.
  • If yes, than you need to change the configuration of Azure Load Balancer.

How to change the default idle timeout
This configuration can be made at TCP level, changing the TCP timeout. In this moment this configuration is supported for VMs, Web Roles, Worker Roles and NOT for Azure Web Apps (Azure Web Sites). The maximum value that is acceptable is 30 minutes.
Based on your needs you can increase or decrease this value. Before doing this, at the first release of your system you should identify what is the best value for your system, based on your business use cases and client requirements.

Settings this value cannot be made directly in the portal. This configuration can be made from Powershell or .csdef file. For more information related to how you can configure it - https://azure.microsoft.com/en-us/blog/new-configurable-idle-timeout-for-azure-load-balancer/

An useful PowerShell command is Get-AzureEndpoint. This will retrieve all the configuration of the endpoint, including "IdleTimeoutInMinutes".
Get-AzureVM –ServiceName “FooService” –Name “FooVM” | Get-AzureEndpoint

The takeaways of this post are:

  • 502 is caused in general by a timeout
  • The timeout can be configured at endpoint level
  • The timeout cannot be configured 
Labels:

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...
Post a Comment
Read more