Previously deployed index.html still gets served
Hey all,
I had my page running as a react app with a index.html.
I now moved to remix with a server side rendering approach.
Now, if i go to https://portcity-ai.com/ I still get served the old index.html. If I go to a path https://portcity-ai.com/services i get the new result from the route handler.
I tested it by pushing a bare minimum index.html - and now I get that one served - even after deleting it.
I cleared the cache but that doesn't help. Any ideas?
I cleared the cache but that doesn't help. Any ideas?
Portcity AI - We are your AI Transition Partner - Leading AI Soluti...
Transform your business with cutting-edge AI solutions. Expert consulting, chatbot development, and automation services in Mobile, AL.
Portcity AI | Your AI Transition partner
Discover the range of AI services offered by Portcity AI. From AI consulting to chatbot development, we provide tailored solutions to meet your business needs, including workshops and team-specific trainings, use case analysis for where AI is best suited for your business, and custom implementation.
10 Replies
I temporarily solved it by adding a /start route and then publishing a index.html that does a html redirecto to /start.
ten I removed the index.html again.
Now I sstill get the index.html with the redirect served, even though its no longer present in the deployment
just found this:
https://community.cloudflare.com/t/custom-domain-not-reflecting-updated-cf-pages-app/618259
I was about to post the same question here. Facing identical issue, moved a bunch of pages from
/slug1/ to /slug2/ on the website, and after succesful deployment /slug1/ is still server from the main domain. Clearing cache, etc. didn't help. slug1 also doesn't exist on *.pages.dev subdomain, only on the main domain. Looking at the discussions online, there's no resolution to this issue other than just waiting?
Another unexpected thing is that sometimes even older versions of this page is served, e.g. from deployment a few days agoprobarly cloudflare cached it
Yea, but I how do I tell it to forget about it?
Clearing the cache doesn't do anything
In our case the page was gone from edge servers in about 24h. The most concerning side-effect was that on 2 different edge-servers we had different versions of this page cached, so users were serving different outdated versions and we didn't have any control over it. I'm wondering what's the best workaround for cases when we really need to remove the page asap - setup custom redirect for those pages maybe 🤔
you can disable caching in cloudflare and create a header to prevent it from being cached in user browser also
browser cached it
Still got issue?
It isn't browser caching (different browsers or incognito windows show the same) or regular CF cache (purging everything didn't help either as noted by Dom above). It's probably related to https://developers.cloudflare.com/pages/configuration/serving-pages/#asset-retention
can be
i never had this problem
It wasn't for me.
I had the same problem across multiple browsers, incognito windows and devices. It was definitely CF serving the file.
As @sergey said - it's probably asset retention related.
Would be good to get a way to tell CF to wipe all retained assets.
I even thought about killing Page and setting up a new one on the same url but I didn't wana risk further problems.
On a 'fun' note - while for me the issue seemed to be resolved now, The other day a ghost index.html appeared again after things were working for days.
I published and then deleted anoter redirecting index.html and for now, it's resolved.