It has been nearly 30 hours since I posted this critical routing issue, and I have not received any response. The custom domain is still showing 404 while the .vercel.app URL is fully functional. This is severely impacting my project. Please escalate this infrastructure matter."

Your deployment itself looks healthy, the key proof is that your Vercel preview URL loads correctly and serves index.html. That confirms the build, framework output, and promotion to production are working as expected.

When a custom domain shows 404: not_found while the Vercel URL works, the issue is almost always domain configuration or DNS propagation, not the deployment.

Hi Will Smith/Vercel Support Team,

Thank you for your response. My deployment status is "Ready" and it works on the Vercel preview URL, but my custom domain (onyx-drift.com) is still showing a 404: NOT_FOUND error.

Here are my project details for your investigation:

1. Project Structure: My app is located in a /client subdirectory.

2. Build Tool: I am using Vite, and the output is generated in the client/dist folder.

3. Configuration: I have already added a vercel.json with proper SPA rewrites.

4. Nameservers: I have already pointed my domain nameservers to Vercel (md-link-1, md-link-2).

Could you please check if there is an issue with the Root Directory mapping or DNS propagation for my account?

Looking forward to your help.

Best regards, shakib

Issue: I am experiencing a 404 error when accessing routes directly (e.g., /profile). My project is a Vite-React app located in a subdirectory called client.

Configuration details:

1. Root Directory is set to client in Vercel settings.

2. vercel.json is located in the client folder with the following content: { "rewrites": [{ "source": "/(.*)", "destination": "/index.html" }] }

3. Build output directory is dist.

4. Deployment is successful, and the homepage works, but internal routing fails on page refresh.