![opendrive error 502 opendrive error 502](https://bloggingrevolution.com/wp-content/uploads/2021/06/502-Bad-Gateway-Error-1-1024x576.jpeg)
On the Azure Portal, on your app’s blade, you have the options to stop or restart your app. This is often the simplest way to recover from one-time issues. NET one.įor more information, see Auto-Healing Azure Web Sites. Note that these settings would work in the same way even if your application is not a. All you need to do is add some triggers in the root web.config for your app. Though you can always restart the app from directly within the Azure Portal, AutoHeal will do it automatically for you. Most of the time, recycle the process is the fastest way to recover from a problem. Use AutoHealĪutoHeal recycles the worker process for your app based on settings you choose (like configuration changes, requests, memory-based limits, or the time needed to execute a request).
OPENDRIVE ERROR 502 MANUAL
You can set the scaling to be Manual or Automatic. If the process goes down on one instance, the other instance will still continue serving requests. This not only provides you with more processing capability, but also gives you some amount of fault tolerance. Scaling up an app involves two related actions: changing your App Service plan to a higher pricing tier, and configuring certain settings after you have switched to the higher pricing tier.įor more information on scaling, see Scale an app in Azure App Service.Īdditionally, you can choose to run your application on more than one instance. In Azure App Service, for increased performance and throughput, you can adjust the scale at which you are running your application. These memory dumps are snapshots of the process and can often help you troubleshoot more complicated issues with your app.įor more information on features available in Kudu, seeĪzure Websites online tools you should know about.
![opendrive error 502 opendrive error 502](https://kinsta.com/wp-content/uploads/2017/09/502-bad-gateway-error-chrome.png)
When you do run into issues with your app, the diagnostics tool will point out what’s wrong to guide you to the right information to more easily and quickly troubleshoot and resolve the issue. Some of the metrics that you might want to monitor for your app areĪpp Service provides an intelligent and interactive experience to help you troubleshoot your app with no configuration required. The Metric blade will show you all the metrics you can add. In your app’s blade, click the Requests and errors tile. This option enables you to find out if your application is having any issues. For more information, see Track service health. You can track the health of the service on the Azure Portal.
![opendrive error 502 opendrive error 502](https://www.errorvault.com/en/images/runtime-errors_error-502_utorrent-error-502.png)
![opendrive error 502 opendrive error 502](https://mediendesign-quer.com/wp-content/uploads/2017/07/502-error.jpg)
Microsoft Azure publicizes each time there is a service interruption or performance degradation. Observe and monitor application behavior Track Service health Observe and monitor application behaviorĪpp Service gives you various options at each step.ġ.Troubleshooting can be divided into three distinct tasks, in sequential order: Troubleshooting steps to solve "502 bad gateway" and "503 service unavailable" errors application crashing due to an exception.This problem is often caused by application level issues, such as: When you browse to the app, it returns a HTTP "502 Bad Gateway" error or a HTTP "503 Service Unavailable" error. Go to the Azure Support site and click on Get Support. Alternatively, you can also file an Azure support incident. If you need more help at any point in this article, you can contact the Azure experts on the MSDN Azure and the Stack Overflow forums. This article helps you troubleshoot these errors. "502 bad gateway" and "503 service unavailable" are common errors in your app hosted in Azure App Service.