Skip to main content

Deployment fails because the environment disk is full (DeploymentUpdateSiteExtensionGitPushFailed)

Why a Cloud deployment fails with an empty git push error or a "not enough space" message, how to check disk usage, and how to free space.

Written by Joana Knobbe

Type: Troubleshooting
​Category: Umbraco Cloud > CI/CD & Deployments
​Tags: DeploymentUpdateSiteExtensionGitPushFailed, git push failed, empty error message, disk space, disk full, not enough space on the disk, NuGet cache, .nuget, log files, Preparing Deployment
​

Product: Umbraco Cloud
​Version: All versions


Symptoms

  • A deployment between environments fails with:

[DeploymentUpdateSiteExtensionGitPushFailed] The git push operation failed, message is ''
  • The message is empty. That is expected for this error.

  • The deployment stops at Preparing Deployment, and Log Streaming in Kudu stays empty.

  • You may also see There is not enough space on the disk, logs that won't load, or a site that won't start.

  • Removing lock files in site/locks doesn't help, and often there aren't any.

Cause

Each Umbraco Cloud environment has a disk quota that depends on your plan. You can see the quotas under Plan quotas. When an environment reaches its quota, write operations fail, and a deployment to that environment can't start.

The space usually goes to one of these:

  • The NuGet package cache, which keeps old package versions after many upgrades.

  • Log files.

  • Temporary files.

Umbraco Cloud now removes unused NuGet packages automatically after each successful deployment. If the disk is already full, that deployment can't run, so the first cleanup has to be done by hand.

A full disk is a common cause of this error, but not the only one. If disk usage looks fine, contact support with the error and the environments involved.


Solution

Step 1 — Check disk usage

  1. In the Umbraco Cloud Portal, open your project and go to Insights > Usage.

  2. Under Collected for insight, check disk usage. Look at the environment you are deploying to, not only the one you are deploying from.

Don't rely on Kudu's Environment tab for this. The disk figures there show the underlying Azure storage, not your plan quota. They can look fine while the environment is full.

Step 2 — Clear old log files (you can do this yourself)

Delete old log files on the affected environment, then restart it. See How can I manage logs and optimize disk usage in Umbraco Cloud? Delete only log files.

Step 3 — Clearing the NuGet cache (ask a supporter first)

If the logs aren't the problem, the fix we usually apply is to clear the environment's NuGet package cache. It is normally safe: the packages are downloaded again on your next deployment, which then takes a bit longer. Before anything is deleted, a supporter should confirm that this is what's using the space.

Please don't delete folders in Kudu on your own to free space. If you are chatting with Umboto, type "talk to human". Otherwise, contact us through the messenger. Tell us which environment is affected, and invite support to the project so we can check it.

Step 4 — Deploy again

After the cleanup, restart the environment, wait about 10 minutes and run the deployment again.


Keep it from happening again

  • Remove old log files regularly, and don't log more than you need.

  • Don't store large files on the environment's disk.

  • If you keep running close to the limit, consider a plan with a larger disk quota.


Still having issues?

  • If you are chatting with Umboto right now, type "talk to human" and we will connect you with someone who can help.

  • If you are reading this article in the Help Center, contact us by clicking the messenger icon at the bottom right.

Related articles

Recommended documentation


Last updated on November 03, 2026

Did this answer your question?