Topic: Production App Suddenly Broken: CSS/Assets Not Loading (Plain Text Appearance) - Despite Locked Deploy

:hammer_and_wrench: Topic: Production App Suddenly Broken: CSS/Assets Not Loading (Plain Text Appearance) - Despite Locked Deploy

Hello Netlify Community,

I am encountering a critical issue with my production deployment that started suddenly a few hours ago, even though I have locked auto publish and have not manually deployed a new version.

The Problem

My application, which was working perfectly fine for days after its initial publication via GitHub, suddenly appears completely broken in production.

  • Symptom: The app displays as plain, unstyled text.

  • Impact: All backgrounds, CSS, images, and other assets are not loading. It appears that the browser is failing to fetch any required resources.

  • Visual: The site looks exactly like an HTML file with no styling applied.

:stop_sign: Key Details and Context

  1. Deployment Method: I initially published the app a few days ago through GitHub integration.

  2. Deployment Status: My production deploy is set to the last known working deployment and is marked as stable.

  3. Auto Publish: I had locked auto publish specifically to prevent accidental production updates.

  4. Timeframe: The issue began suddenly a few hours ago. No new code was merged to the production branch, and no new deploys were published to production since it was locked.

  5. Site Names:

    • sqlcasefiles.netlify.app

    • sqlcasefiles.com

What I Have Tried

  • Clearing my browser cache.

  • Checking the deployment logs (no new deploys visible).

  • Checking the deploy summary in Netlify (it confirms the working deploy is published).

Hi!
Have you tried to check your css and assets paths, as they update after the deployment. You may also try to run your site locally to check if all css is generated. Hope it will helps, thanks!

Hi, @darpan_bhadra. I believe this is because your CSS uses cdn.tailwindcss.com and that is hosted using Cloudflare.

So, yes, you CSS wasn’t working but, no, Netlify did not cause it in any way.