Getting timed out connection when deploying to Azure app service

Question

We're attempting to deploy our application to our Azure Web App. This is an application that we've had hosted in Azure for many years now, and have a staging and production slot. Typically we deploy to the staging slot, swap and confirm functionality. Should the application be error prone we can quickly revert back to the previous version. We've been attempting to deploy via our Azure DevOps pipeline, and it's timing out. We decided to try the "old fashioned way" and Publish via Visual Studio, however we're facing the same issue. The error is pretty simple:

12>Start Web Deploy Publish the Application/package to https://mywebsite-staging.scm.azurewebsites.net/msdeploy.axd?site=
12>C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Microsoft\VisualStudio\v17.0\Web\Microsoft.Web.Publishing.targets(4455,5): Error : Web deployment task failed. (Could not complete the request to remote agent URL 'https://
12> 
12>Could not complete the request to remote agent URL 'https://mywebsite-staging.scm.azurewebsites.net/msdeploy.axd?site=mywebsite__staging'. 
12>The operation has timed out 
12>Publish failed to deploy. 
12> 
========== Build: 11 succeeded, 0 failed, 3 up-to-date, 0 skipped ========== 
========== Build started at 11:25 AM and took 02:51.582 minutes ========== 
========== Publish: 0 succeeded, 1 failed, 0 skipped ========== 
========== Publish started at 11:25 AM and took 02:51.583 minutes ==========

So what's interesting is that when I go to "https://mywebsite-staging.azurewebsites.net" the website loads (slowly). When I attempt to go to "https://mywebsite-staging.scm.azurewebsites.net" to enable logging, I get a 503 unavailable. It feels to me like our staging slot is "sick". I don't know what corrective action we could take against it however. Thoughts on resolutions? We're restarted the web app, but that's about all I see we can do administratively. Should we perhaps create a new staging slot, delete the old and try deploying to that?

Answer 1

Hi Eric, As you're unable to open the Kudu console, the only other option I could think of enable the diagnostic logging for the web app and check the log for errors.