I changed our domain to .com from .xyz
Unanswered
American black bear posted this in #help-forum
American black bearOP
I get this persistent chunk errors for over 12 hours now and everyone can't access the website because of this. In cloudflare when I turn on development mode it goes away so it seems it's some sort of cache issue.
We've been using .xyz domain for 2 years now and moved to .com 12 hours ago. What is going on with next?
We've been using .xyz domain for 2 years now and moved to .com 12 hours ago. What is going on with next?
45 Replies
American black bearOP
I've also tried the purge everything button in cloudflare cache settings and it doesnt last as a few minutes later this same error screen pops up.
But then if I manually go to a different url (random) sometimes the page works
Then i try navigate with the internal navigation already present on the working page the issue is back
This doesnt make sense
American black bearOP
bump
American black bearOP
had to turn off cf proxy :/
@American black bear had to turn off cf proxy :/
did it work then
there must be a option to clear cache in cf
American black bearOP
There is but it never worked fully
it just broke again
so i just turn off cf proxy now
Netherland Dwarf
check your code and hosting
and try find your old .xyz domain
and remove the old builds cache
@Netherland Dwarf and remove the old builds cache
American black bearOP
we deploy to railway, idk how I'd find the old build cache there
I don't think it's possible
@American black bear we deploy to railway, idk how I'd find the old build cache there
Netherland Dwarf
It's better to use render.com
@Netherland Dwarf It's better to use render.com
American black bearOP
How come
@American black bear How come
His message is not relevant to the solutoin
@American black bear so i just turn off cf proxy now
So if it works fine when CF proxy is off, then the problem is with caching in cf
thats it
@Anay-208 So if it works fine when CF proxy is off, then the problem is with caching in cf
American black bearOP
I purge the cache but then it keeps coming back
Doesnt come back immediately
But like 5-10 min later
From the purge
Idk if it's a user who gets the error and it propagated to everyone else
That wouldn't make sense
@American black bear I purge the cache but then it keeps coming back
hmm, ya it could be railway too in that case, as its caused due to some cache revalidation mismatch(even idk why this happens)
Try looking for smthing on railway
some forum or maybe in cf forum with the same issue
try asking claude to research, its also good at it
American black bearOP
So i tried turning on railways new cdn cache powered by fastly instead of using cf and yeah the issue also came back for that
if you're already using cdn cache
American black bearOP
Im not
I tried to*
Oh
American black bearOP
No cdn caching is on rn
Cause of that chunk error
I'll get back to u
American black bearOP
Alr
Is there a chance your browser is doing some caching?
Like that cf setting could be affecting the headers too so it force gets new instead of hoping
Oh wait thats the rsc payload, for nextjs that can run under same url so if its not careful, then it'll cache it instead of the normal page
@American black bear So i tried turning on railways new cdn cache powered by fastly instead of using cf and yeah the issue also came back for that
Yeah i think theyd have same issue here, I think you just need to only let static assets get cached and ignore normal pages