Question

Different file versions in different geographical locations

On 2 separate occasions now, I’ve uploaded a file to a droplet from my location in Canada, but users viewing the site in the UK are seeing the old version of the file.

The first time this happened I uploaded a stylesheet. The stylesheet updated for me and other users in North America, but users in the UK were still being served the original stylesheet, even after clearing their browser caches. In this case, I restarted the droplet which fixed the issue.

The second time this happened was 2 days ago, I uploaded an updated logo in svg format. I deleted the original file and uploaded the new one which had the same filename and path. I could see the updated logo along with other users in North America, but users in the UK were still seeing the original logo. In this case, I don’t know if they cleared their caches or if a droplet restart fixed the issue.

I was hoping someone had an explanation for why this happens, and how to avoid it in the future?


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

This could be somewhat normal. But without some sort of setup explanation nobody can say for sure.

Especially if you are using CDN, something like CloudFlare, it can happen. For example on CloudFlare, you can purge cache manually.

This can also depend on server caching settings and user browser. Make sure that users clear browser cache.

Maybe you can try not using files with same name. If you cache assets only, that could potentially work.