React Application successfully deployed in Web App, but Web App returns error

Question

I have a React - Vibe application and I can successfully build a disk folder (npm run build) and deploy the disk folder to two Azure web apps.

One of them simply works and the other one never worked and its log seems to raise error! Log is attached.

2025-06-02T105844.5125894Z Deploy A.txt

Answer 1

Hi @Intelicosmos ,

I’m glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!

Since the Microsoft Q&A community has a policy that “The question author cannot accept their own answer. They can only accept answers by others”, I’ll repost your solution in case you’d like to Accept the answer.

Issue:

While deploying a React application (built with Vite) to an Azure Web App on the Free Tier (F1, Linux), the deployment failed with the error:

“There is not enough space on the disk”

This error occurred during a ZIP deployment using az webapp deployment source config-zip, even though the same deployment worked fine on a different Web App instance.

Investigations showed:

• The React dist folder included a large 56 MB video file.
• F1 tier Web Apps have limited disk space, often less than 1 GB.
• The deployment process temporarily doubles the required space due to ZIP extraction and cleanup.
• F1 Linux plans do not expose the Kudu/SCM console in the Azure portal.
• The failing Web App had a hostname with a random suffix (e.g., *.azurewebsites.net), which is expected behavior for F1 Linux plans.

Solution:

I can confirm that after moving videos to Blob Storage and using video Urls, I was able to successfully deploy to Web App.

To resolve the issue Removed the large video file from the React dist folder and Uploaded the video to Azure Blob Storage instead.

Then Updated the React app to reference the video via Blob Storage URL, rather than packaging it with the app.

After this change, the application deployed successfully to the Free Tier Azure Web App without disk space issues.

---

Please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.

Answer 2

Intelicosmos, As I mentioned in my previous response, the long “-ambedgapeef8g6f6.australiaeast-01.azurewebsites.net” hostname and missing SCM link mean this is a Linux Free-Tier (F1) Web App not a Windows one. On F1/Linux:

• Azure always adds that random stamp to the URL, so you won’t see partner…​.azurewebsites.net. Your address will look like partner…-<randomstamp>.<region>.azurewebsites.net.
• The portal does not show an SCM/Kudu endpoint for Linux F1, so you cannot browse to yourapp.scm.azurewebsites.net. That is by design.

Because there is no IP blocking (your network screenshots confirm that) and you are not hitting any subscription limit (Azure lets you create up to 10 Free-Tier Web Apps per subscription), you can ignore those concerns. You simply need to deploy your React/Vite files with the method I described earlier:

1. Zip the contents of your local dist folder so that index.html and its assets/ folder live at the root of the ZIP (no extra “dist” wrapper).
2. Run:

      az webapp deployment source config-zip \
      --resource-group YourResourceGroup \
      --name partner… \
      --src path/to/app.zip
      
   

3. Keep the Startup Command blank under Configuration < General settings so Azure’s built-in static host (/opt/startup/default-static-site.js) serves your index.html.

Once you do that, your React app will load at the Linux hostname instead of showing the default page. If you need a simpler partner…​.azurewebsites.net address or want Kudu access, you’d have to switch to a Windows-based F1 plan or move up to a Basic (B1) Linux plan.

Answer 3

Hi Intelicosmos,

That “not enough space on the disk” error is happening because your Free-Tier Web App simply doesn’t have room for a 56 MB video plus all your static files. On F1 (Linux or Windows), App Service gives you only a few hundred MB (often under 1 GB) of total storage and the ZIP extraction briefly needs nearly double the package size to unpack before cleaning up.

You can prove it out by removing that video from your dist folder and redeploying. As soon as the package size drops back into the App Service’s quota, your ZIP deployment will succeed.

For anything that large, you have two practical options:

Offload the video to external storage. Upload the MP4 to Azure Blob Storage (or Azure CDN, or even YouTube/Vimeo) and then reference its URL in your React app. That keeps your Web App lean, fast, and under the Free-Tier storage limits.

Upgrade your App Service plan. Move off F1 into a Basic (B1) or higher tier. Paid tiers give you several GB of disk and plenty of headroom for large assets.

Once you either remove or relocate that 56 MB video or bump to a paid SKU you’ll find your ZIP deployment of the remaining files will finish without the disk-full error.