Hi, I’m not sure if this is a Netlify issue, Gatsby issue, or both. Since switching my site over to a Gatsby build, whenever I go to my public domain, an old cached version of my site loads first. I have to hard reload to see my updated site. (MacOS Catalina, Chrome Version 80.0.3987.132) I have…

[image] marguerite: marguerite.io so, the content still exists on the cdn nodes - you deploy to origin, and then it gets pushed out to the edge. so that’s actually not surprising. It won’t get deleted unless you delete the netlify site. Is the .wtf site the correct site, now? This is what i …

hey @marguerite , welcome. Are you seeing this in an incognito window as well? I am wondering if this is a browser caching issue.

Hi @perry , thanks for the reply! I am not seeing the issue in an incognito window. (:clap:) But clearing the caches don’t seem to work (iirc). The bigger problem is that it is happening to other people who visit my site, and they just think it hasn’t been updated in x-amount of time. They don’t fe…

hmm. if you are seeing the correct version in an incognito window, and others are also seeing the right one, then that basically rules out anything but a local browser issue which we can’t really help you with. Some ideas: have you tried a different browser? what happens when you try and view the …

I’m sorry—I worded that last part strangely. Others are seeing the wrong version now if they had visited my site prior to the Gatsby redesign. The site displays correctly on my phone and other browsers. (Thank you! His name is Oscar.)

Maybe it’s caused by an aggressive service worker? I don’t see any, but that doesn’t mean one hasn’t been registered before…

ah, so it could be more wide spread than local. Seems like maybe I weird question, but humour me: Are the other people who are seeing the old site using the same internet service provider? We had a weeeeird bug a while back where everyone who was using a specific local ISP was having problems. And …

The issue is happening across ISPs. I don’t believe I’m using a service worker. How do I more thoroughly check that? (Checked using the service worker detector chrome extension and nothing is detected.)

have you tried deploying the same code to a completely new site and seeing if that fixes the issue? [image] [Support Guide] Understanding & unregistering service workers Support Guides Last reviewed by Netlify Support - August, 2023 A service worker is a script that your…

That’s a good idea. I just removed all instances of netlify from marguerite.io’s nameservers and deployed the code to marguerite.wtf . Even with everything removed from marguerite.io, I still see the old, pre-gatsby, version of the site on marguerite.io . So this must be a caching issue with my doma…

That seems to have worked! :raised_hands::raised_hands: Thank you @perry and @tomrutgers for all the help! Much appreciated.

Netlify + Gatsby serves old/cached (pre-Gatsby) version of site

Support

perry March 13, 2020, 4:59pm 9

have you tried deploying the same code to a completely new site and seeing if that fixes the issue?

Topic		Replies	Views
Cached version of website not updating on new build/repo change Support deployment	6	3369	December 28, 2020
Product Pages and Images Not Loading Properly after moving to @netlify/gatsby-plugin Support deployment , gatsby , caching	5	569	December 28, 2023
Should Netlify clear cache when I upload from Gatsby Cloud? Support deployment	1	1199	May 21, 2020
About caching gatsby pages Support caching	8	1882	February 12, 2021
Gatsby-WordPress site only loads on a fresh browser session & immediately fails on any successive visit Support netlify-dns-https-ssl , gatsby , caching	17	2011	June 25, 2021

Netlify + Gatsby serves old/cached (pre-Gatsby) version of site

Related topics