Azure Web App Deployment Stuck with Microsoft.Web/serverfarms sh

ghz 8months ago ⋅ 72 views

Azure Web App Deployment Stuck with Microsoft.Web/serverfarms showing BadGateway status

I'm currently working on deploying a website developed with ASP.NET 8.0 using Azure Web App Services and have encountered an issue that I'm unable to resolve. I use the Azure subscription 1 plan which is the free plan with 200$ free.

Here are the steps I've followed:

  1. Created a Resource Group.
  2. Created a SQL database.
  3. Attempted to create a Web App in App Services.

During the Web App creation step, I ran into a problem. After configuring the settings with the Free F1 plan of Azure and clicking 'Create', I noticed in the results that all components were created successfully (showing an 'Ok' status), except for Microsoft.Web/serverfarms, which showed a BadGateway status. The deployment process seems to hang at this point, with no further progress even after a significant amount of time.

enter image description here

I've tried several troubleshooting methods and searched extensively for solutions, but haven't been able to resolve this issue. Has anyone else encountered this problem, and if so, how did you manage to solve it? Any help would be greatly appreciated.

Answers

It seems like you're encountering an issue during the creation of the Azure Web App service plan (Microsoft.Web/serverfarms) within your Resource Group. Here are some steps you can take to troubleshoot and resolve this problem:

  1. Check Resource Group Quotas: Ensure that you have not exceeded your Azure subscription limits or resource group quotas. The Free F1 plan has certain limitations, so it's possible that you've reached a quota limit. You can check your subscription quotas in the Azure portal by navigating to "Subscriptions" > "Usage + quotas".

  2. Review Deployment Logs: Azure provides detailed deployment logs that can help identify the cause of the issue. Navigate to your Azure Resource Group in the Azure portal, select your Web App service plan, and then click on "Deployment Center" or "Activity log" to view deployment logs. Look for any error messages or warnings that might indicate the cause of the problem.

  3. Check Network Connectivity: Sometimes, network connectivity issues can cause deployment failures. Ensure that your network connection is stable and that there are no firewall or proxy issues blocking communication with Azure services. You can also try deploying from a different network or using a VPN.

  4. Retry Deployment: Sometimes, deployment failures can occur due to transient issues in the Azure infrastructure. Try deleting the failed deployment and reattempting the deployment process. This can sometimes resolve the issue if it was caused by a temporary glitch.

  5. Contact Azure Support: If you're still unable to resolve the issue, consider reaching out to Azure support for assistance. They can provide additional troubleshooting steps and guidance tailored to your specific situation.

By following these steps and carefully reviewing deployment logs, you should be able to identify and resolve the issue preventing the creation of your Azure Web App service plan. If you encounter any specific error messages or issues during the troubleshooting process, feel free to provide more details, and I can offer further assistance.

#asp.net