Hi @educatedsuddenbucket. It looks like the files are being added to the /public directory, so that would need to be included in the address path. For example, my-awesome-site.com/public/1 rather than my-awesome-site.com/1

You could configure rewrites to remove the /public segment from the path. Or you could change the way your project builds these files.

If you need help setting it up, please share a minimal reproducible example so we can make specific recommendations that will work for your repo.

I cannot provide a reproducible example here because my code uses the GitHub api,but I can give you a reproducible example somewhere where conversation is private , but here is some info My vercel.json is this

1
{
2
  "version": 2,
3
  "builds": [
4
    {
5
      "src": "server.js",
6
      "use": "@vercel/node"
7
    },
8
    {
9
      "src": "public/**/*",
10
      "use": "@vercel/static"
11
    }
12
  ],
13
  "routes": [
14
    {
15
      "src": "/api/(.*)",
16
      "dest": "/server.js"
17
    },
18
    {
19
      "src": "/create",
20
      "dest": "/server.js"
21
    },
22
    {
23
      "src": "/(.*)",
24
      "dest": "/public/$1"
25
    }
26
  ],
27
  "regions": ["bom1"]
28
}

I have tried to access my html with these url paths /1 , /1.html , /public/1 , /public/1.html

Also the other html and asets u see like manage.html , manage.js , work and were pre included in the code and were not generated through build

It's been a few days. Thanks for your patience. I hope you found a solution and you're not still stuck.

If you still need help, a minimal reproducible example would let us both work from the same code so we can debug this together. If you can share one, I'm happy to take a closer look.

If you prefer to debug on your own, I find the Output info on the Source tab very helpful. That will show you the file structure as it is deployed so you can see which paths exist. I also wrote a more detailed post to help with 404 errors. That's also worth a read if you're still having trouble with this.

https://community.vercel.com/t/debugging-404-errors/437

Vercel Community

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are...