Persistent 404 Error

I’m encountering a persistent issue with my project hosted at https://procxima.com, specifically when trying to access the route https://procxima.com/services. Despite multiple redeployments and configuration changes, the route consistently returns a 404: NOT_FOUND error, even though it’s correctly defined in my React SPA.

Here’s everything I’ve done so far: :white_check_mark: Deployment & Build Using Vite (v5) and React Router DOM v6

Production build runs successfully: vite build outputs to /dist

Confirmed that /dist/index.html is generated

Vercel build logs show successful deployment

:white_check_mark: Routing Configuration vercel.json is present in the root and contains:

json Copy Edit { “rewrites”: [ { “source”: “/(.*)”, “destination”: “/index.html” } ], “trailingSlash”: false } vite.config.js has:

js Copy Edit server: { historyApiFallback: true }, build: { outDir: ‘dist’ } React routing in App.tsx includes a properly defined

Using BrowserRouter, not HashRouter

:white_check_mark: Redeployments Performed multiple “Redeploy with clear cache” from the dashboard

Also did a manual empty commit to GitHub:

bash Copy Edit git commit --allow-empty -m “force clean deploy” git push Purged the Data Cache from the Vercel dashboard

Output directory is set to dist in project settings

:white_check_mark: Verified Locally Local dev server works fine at /services

Local production build works when index.html is served via a static file server

:cross_mark: Still Failing Visiting https://procxima.com/services directly always shows a 404

Even with all rewrites in place, Vercel does not serve the SPA fallback (index.html)

curl -I https://procxima.com/services returns:

go Copy Edit x-vercel-error: NOT_FOUND :magnifying_glass_tilted_left: My Conclusion Everything works as expected locally and the project is correctly structured for a static SPA deployment. However, something on Vercel’s end — potentially a CDN caching issue or a project-level configuration override — seems to be preventing the fallback routing to index.html.

:wrench: Request Could you please:

Check if any internal settings (or legacy caches) are overriding my vercel.json rewrite?

Help diagnose why the rewrite for /services isn’t serving index.html, even though all indicators say it should?

Provide any internal logs that show why the fallback failed?

Project Details:

Domain: https://procxima.com

Problem URL: https://procxima.com/services

GitHub Repo: https://github.com/arnavkudale/PROCXIMA

Framework: Vite + React SPA

Deployment Platform: Vercel

There’s another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Hey, @arnavkudale! Welcome to the Vercel Community :waving_hand:

Did you manage to find a fix for this? I see that your site is resolving as expected.

No, any other page apart from home page when refreshed shows this.

Have you taken a look at this thread to help you debug?

Hi @arnavkudale , I can’t access your repository. Can you share a public link?