Droplet NGINX serving old cached content after deploy how to clear cache reliably?

Hi all,

I’m running into an issue with an NGINX web server on a DigitalOcean Droplet where, after a new deployment, some users are still seeing old cached content even though the files on disk are updated. This seems to affect CSS/JS and some template files.

Here’s the setup: • Ubuntu 22.04 droplet • NGINX 1.18 configured with expires headers for static assets • No CDN in front of the server (just Cloudflare DNS) • PHP backend (FastCGI) serving dynamic content

After pushing a new release (updated CSS and template changes), everything looks correct when I test directly on the server or with curl, but some visitors report seeing the old styles and minor layout issues. Restarting NGINX doesn’t seem to fix it for all users immediately, and I’m not sure if this is being cached at the browser level, somewhere in NGINX, or both.

What I’ve tried so far: • Clearing NGINX fastcgi cache (if any) • Setting add_header Cache-Control no-cache for testing • Bumping static asset filenames with version query params

Still, recurring complaints about stale content persist.

For context, I manage deployments for sites like Rincon Family Dentistry, and consistent user experience across deploys is important to us, so I’m trying to understand reliable cache control practices here.

Has anyone dealt with late‑cache issues like this on a DigitalOcean Droplet with NGINX? Are there NGINX settings or best practices you recommend to ensure updated content is served immediately after a deploy?

Thanks in advance!