Purge all cache resulting 404 Not Found nginx/1.10.0 (Ubuntu)

When making small adjustments in my website, to see them live I have to purge all cache. The result is several pages with 404 Not Found nginx/1.10.0 (Ubuntu) error messages, and several minutes for all pages go live again.

Yesterday when changing a css from h3 element in my homepage, I tried to purge only the homepage css file (ex: https://www.mywebsite.com/wp-content/cache/min/1/86e206f2f013e78815bc7b77a3fb5f65.css) but several pages were misconfigured, so I had to expire all cache again just to apply this small css adjustment.

Some hours ago I changed a line on header.php file, and I was wondering if there is a way to purge the cache without impacting all website pages causing server overloading. In this case should I purge only https://www.mywebsite.com/wp-content/themes/mytheme/header.php file?

Another doubt… when making small changes on CSS, what is the best way to purge the cache to avoid server overloading and consequently 404 Not Found error messages?

Hi @galgarpia,

Most (if not all) issues here are related to your origin server and CMS and how they handle certain changes. There may be misconfiguration at play, as purging all should not be reason for your server to be “overloaded”, let alone returning 404s instead of 5xx internal error status codes.

You’d have a better chance of fixing these issues by asking your hosting provider support for help. If you think specific Cloudflare features may be what is causing the server overload, you’d increase your chances of getting help here by being specific and providing more details such as what page rules you have, what’s your caching level etc.