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.

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

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

@rekflow It looks like the "Configuration Settings in the current Production deployment differ from your current Project Settings." Can you please check your configuration settings and Vercel.json and check if both matches.

Thank you @neerajkumar61. I've tried troubleshooting how to fix this discrepancy but I've come up empty. Here is what is in my vercel.json file

1
{
2
  "version": 2,
3
  "builds": [
4
    {
5
      "src": "frontend/package.json",
6
      "use": "@vercel/next"
7
    },
8
    {
9
      "src": "api/index.py",
10
      "use": "@vercel/python",
11
      "config": {
12
        "maxLambdaSize": "15mb",
13
        "runtime": "Python 3.12.4"
14
      }
15
    }
16
  ],
17
  "routes": [
18
    {
19
      "src": "/api/(.*)",
20
      "dest": "/api/index.py"
21
    }
22
  ],
23
  "rewrites": [
24
    {
25
      "source": "/api/:path*",
26
      "destination": "/api/index.py"
27
    },
28
    {
29
      "source": "/(.*)",
30
      "destination": "/frontend/$1"
31
    }
32
  ]
33
}

[grid] [/grid]