Title: Edge 404 (NOT_FOUND) despite valid alias — possible control plane / edge routing desync

Help
1

Project: cauldron (prj_xwm6bMZgjOohBW06JepYNCxIfFhn)
Team: connr-s-projects
Domain: cauldron.gg (also affects www.cauldron.gg)
Deployment: dpl_FvuZmkTkzw35HBAZR9t4mga8EpQa

Issue

Requests to https://cauldron.gg return a Vercel edge-level 404 with zero serverless function invocations — the request never reaches the deployed app:



HTTP/1.1 404 Not Found

Server: Vercel

X-Vercel-Error: NOT_FOUND

What the API/dashboard reports (all healthy):

  • Deployment is READY with aliasAssigned: true and aliasError: null
  • The alias array explicitly includes cauldron.gg
  • Domain settings show “Valid Configuration”
  • DNS resolves correctly to Vercel edge (216.198.79.1) — confirmed via 8.8.8.8 and 1.1.1.1
  • SSL is valid (Let’s Encrypt, expires Oct 2026)
  • Build log shows Next.js 16.2.9 compiled successfully with all routes including ƒ /

Anomaly:

  • Project framework field is null via the API, despite being a working Next.js 16.2.9 build — potentially related to the routing issue

Evidence it’s not a DNS/code/config issue:

  • Other aliases on the same project work correctly (e.g., git-branch preview URLs serve the app)
  • The problem is isolated to cauldron.gg specifically
  • CLI command vercel alias set reports success, but edge still returns 404 immediately after

Self-service steps already attempted (none resolved it):

  1. Fixed DNS at registrar (GoDaddy) — removed parking A records and Website Builder, added Vercel’s specified A record
  2. Removed and re-added cauldron.gg in Vercel dashboard
  3. Triggered fresh production deployment after domain re-add
  4. Ran vercel alias set cauldron-bn7szytai-connr-s-projects.vercel.app cauldron.gg via CLI — reported success but 404 persists

Conclusion: This appears to be a desync between Vercel’s control plane (API/CLI reporting the alias is set) and the actual edge routing table. The framework: null metadata issue may be related. Requesting investigation into why the edge isn’t reflecting the alias configuration.

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.