Persistent 404 Error on Correctly Configured Monorepo

Help
1

Hello,

I am facing a persistent 404: NOT_FOUND error on a deployment and have exhausted all possible configuration fixes. This appears to be an internal platform bug.

Here is what has been tried and verified:

  1. Project Structure: My GitHub repository has a correct flat file structure with index.html, all artist sub-pages, an /api folder, and a package.json at the root.
  2. Vercel Project Settings: The “Root Directory” is empty and the “Framework Preset” is “Other”. These are correct.
  3. vercel.json Configurations: I have tried multiple vercel.json configurations, from a minimal {"version": 2} to a highly explicit configuration with specific build and route rules. Every attempt still results in a 404 error on the deployed site.
  4. Cache: I have tried redeploying multiple times, including clearing the build cache.

The deployment consistently fails to serve any files (root index.html, subdirectory index.html files, or static assets), resulting in a 404.

Could you please have an engineer investigate this specific deployment?

  • GitHub Repository: GitHub - Nibiru82/hub-artistes
  • Deployment URL: (Mets ici l’URL de ton déploiement, comme https://hub-artistes-xxxxx.vercel.app)
  • Deployment ID: fra1:vqjqk-1751359557435-365486bc0784

Thank you for your help.

2

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.