Why is application deployment failing on waws-prod-blu-167.publish.azurewebsites.windows.net?

Eric Davis 6 Reputation points
2020-03-16T21:27:25.403+00:00

Trying to publish a .NET Core 3.1 app via VS 2019 to Azure using the Publish wizard. Publish process kicks off and runs for a while, but eventually fails with the following error: 

C:\Program Files\dotnet\sdk\3.1.200\Sdks\http://Microsoft.NET.Sdk.Publish\targets\PublishTargets\http://Microsoft.NET.Sdk.Publish.MSDeploy.targets(140,5): Error : Web deployment task failed. (Could not complete the request to remote agent URL 'https://waws-prod-blu-167.publish.azurewebsites.windows.net/msdeploy.axd?site=QAZAuthMvcOidcClient-AS01'.)

Could not complete the request to remote agent URL 'https://waws-prod-blu-167.publish.azurewebsites.windows.net/msdeploy.axd?site=QAZAuthMvcOidcClient-AS01'. The operation has timed out Publish failed to deploy.

I can successfully publish the same application to a different app service instance that is hosted on a different app service plan. That service plan appears to be associated with waws-prod-blu-137.publish.azurewebsites.windows.net, so I assume there is currently some issue with waws-prod-blu-167.publish.azurewebsites.windows.net.

Can someone please take a look???

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,875 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Eric Davis 6 Reputation points
    2020-03-17T13:10:13.593+00:00

    The deployment is really small; < 10MB. WEBSITE_WEBDEPLOY_USE_SCM was set to false. I didn't do this myself. Was set that way be default by the tooling when I stood up the App Service. I changed it to true. I then deleted and recreated the publishing profile and tried again. Now the operation completes successfully.

    The weird thing is that I also deployed this exact same application code to a different App Service / App Service Plan that had the WEBSITE_WEBDEPLOY_USE_SCM value set to false and it works just fine. The only difference appears to be the publishing service associated to the target applications; the one that wouldn't work is associated with waws-prod-blu-167.publish.azurewebsites.windows.net and the one that worked without issue is associated with waws-prod-blu-137.publish.azurewebsites.windows.net.

    Really strange and a huge pain to troubleshoot. Doesn't make any sense.