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.
1 Reply
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