I got an error on uploading the deployment ZIP https://${appName}.scm.azurewebsites.net/api/zipdeploy?isAsync=true
I got an error on uploading the deployment ZIP https://${appName}.scm.azurewebsites.net/api/zipdeploy?isAsync=true
@TonySon-0943 Thanks for reaching out. I understand that you are using Zip Deployment REST API to perform the operation.
In order to troubleshoot your issue further, please help us with the following details:
Is this issue occuring only during deployments or even when accessing the web app in general?
How are you deploying the .zip file: using cURL/Postman/PowerShell?
Are you able to succeed deploying using the ZipDeployUI on the Kudu console, or Azure CLI or PowerShell?
It happened in both cases.
using nodeJS to automate it like below
await fetch(
https://${appName}.scm.azurewebsites.net/api/zipdeploy?isAsync=true,
{
method: 'POST',
body: buffer,
headers: {
Authorization: Basic ${auth},
'Content-Type': 'application/zip',
},
}
)
and it returns
Error: Kudu Zip deploy failed with status 503 and error:
most time I can't access the site. https://${appName}.scm.azurewebsites.net
@TonySon-0943 Thanks for the response. In that case, I believe we'll need to troubleshoot the 503 error with the App Service first.
"503 service unavailable" errors are often caused when there are issues with the application, such as requests taking a long time, application using high memory/CPU, application crashing due to an exception etc.
The simplest check would be to try restarting your web app to see if it helps. Or, if you are on the Free tier, it could be that your app has exhausted its resources and there is a need to scale up the App Service Plan to a slightly higher one, like a Basic/B1 compute tier, say.
If that doesn't help, you could use the diagnostics tool that Azure App Service provides. 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 without needing any additional configuration. To access App Service diagnostics, navigate to your App Service app in the Azure portal, and click on Diagnose and solve problems in the left navigation.
If the issue still persists, you could look at your app's metrics like CPU Time, average memory working set, response times etc. to understand the pattern of the error.
In the case where there is not enough data available, you could enable diagnostics logging for you app to assist with debugging, or instrument your application with Azure Application Insights for enabling detailed performance monitoring.
For more details about each of the above approaches, refer to this article. Hope this helps, do let us know if you have further questions.
If an answer is helpful, please "Accept answer" and/or "Up-Vote" which might help other community members reading this thread.
11 people are following this question.