glen4096
glen4096

Reputation: 874

Azure Devops Pipeline returning: 'Failed to deploy web package to App Service. Internal Server Error (CODE: 500)'

I am trying to use Azure DevOps pipelines to build a .NET 5 (Core) web app and deploy it to my Azure app service. I can't find any complete examples in the documentation that achieve this so I'm following this:

https://github.com/shahedc/NetLearnerApp/blob/main/azure-pipelines.yml.txt

However, the Azure deploy task keeps returning this vague error: enter image description here

In my Azure portal I only get this error: enter image description here

I am assuming the issue is in my pipeline because deployment works when I deploy it directly from the Deployment Center in the Azure portal. Here are the details for the 3 relevant tasks my pipeline:

enter image description here enter image description here enter image description here

Upvotes: 25

Views: 30094

Answers (3)

Allen W.
Allen W.

Reputation: 31

think what Dan Beaulieu said in above answers is correct, but one thing to add, in my case, after deleting the deployments folder, remember to restart the app service/web app, which will make it take effect.

Upvotes: 2

GritKit
GritKit

Reputation: 476

Check if you have disk space available.

Yesterday we started getting this error, even if we tried to re-deploy packages that were successfully deployed just an hour before. Our system guys checked and found out that we reached the space limit and that it was time to upgrade.

P.S. I know that this was answered a long time ago. I am just sharing the solution that was not mentioned here and that worked for us.

Upvotes: 14

glen4096
glen4096

Reputation: 874

I found the solution. It turns out the issue was not in the pipeline, but was caused by a Git connection to the app service I had previously set up in the Azure Deployment Center. Even though I disconnected/removed this Git connection, there was somehow still a residual file left over in Azure that was causing the error. I deleted the 'deployments' folder in Kudu (pictured below) and the pipeline started working as expected.

enter image description here

Getting to the above pictured view:

  • Navigate to your Azure Function project
  • Search for Advanced Tools
  • Open PowerShell

Upvotes: 39

Related Questions