Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
7,763 questions
Error: Error: Failed to upload file 'site/wwwroot/app_offline.htm' from Kudu. Error: Site Unavailable from Mini-ARR (CODE: 503)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 6%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAD%3C/text%3E%3C/svg%3E)
Aniruddha das
1
Reputation point
[error]Failed to deploy web package to App Service.
[debug]Processed: ##vso[task.issue type=error;]Failed to deploy web package to App Service.
[debug]Deployment Failed with Error: Error: Error: Failed to upload file 'site/wwwroot/app_offline.htm' from Kudu. Error: Site Unavailable from Mini-ARR (CODE: 503)
[debug]task result: Failed
[error]Error: Error: Failed to upload file 'site/wwwroot/app_offline.htm' from Kudu. Error: Site Unavailable from Mini-ARR (CODE: 503)
shared app service plan has file storage of 500gb ,in which only 60gb is used.
{count} votes
-
brtrach-MSFT 16,351 Reputation points Microsoft Employee2021-08-04T17:56:28.357+00:00 @Aniruddha das Since nobody from the community reached out to help assist with this, we wanted to share some general steps that can be taken when encountering 503 errors during deployment.
Firstly, depending on the amount of time your deployment takes, we would suggest turning on the 'always on' feature as this seems to have helped others in the past.
The next item is we would ask you to re-look at your app service plan as none of the app service plans offer 500GB of disk space. Disk space sizes are 1GB, 10GB, 50GB, 250GB, and 1TB.
You mentioned this is a shared app service plan. I assume you mean this is a shared tier app service plan, if so, this tier has quota on CPU minutes for 1 hour and 24 hours. Deployments consume a lot of CPU minutes so you might want to consider scaling up to a B1 instance or higher to remove the CPU quotas. (if you meant this is a shared app service plan with multiple sites running on it and you are already running a B1 instance or higher, please ignore this paragraph)
Start with always on and scaling up to see if this resolves the issue. If not, I would suggest checking out the 'diagnose and solve' blade of your web app and use the troubleshooting tool there. More details on that feature can be found here.
Sign in to comment
Sign in to answer