Successful Build Returns 404 Despite Route Output and Domain Alias

Help
1

I’m encountering a persistent issue where a successful build and deployment is returning a 404: NOT_FOUND error both in the preview pane and on my production domain (www.askriggs.com), despite all routes clearly being generated in the build logs.

Key Details:

  • Project Name: firetruck-ai-app
  • Production Deployment ID: J9x5YQReT
  • Git Branch: main
  • Domain: www.askriggs.com and askriggs.com
  • Status: Deployment completed successfully, routes generated
  • Error: Visiting the site or using the preview shows 404: NOT_FOUND

What I’ve Verified:

  • :white_check_mark: All environment variables (e.g., Supabase) are correctly configured
  • :white_check_mark: Build logs show full page generation (e.g., /, /compare, /fire-dealers)
  • :white_check_mark: No middleware or server-side errors
  • :white_check_mark: Domain is verified and aliased
  • :white_check_mark: Promoted directly from known-good deployment

Screenshots & Logs Available:
I can provide full build logs and screenshots confirming successful build and final output (e.g., ○ /compare, ○ /fire-dealers), as well as the 404 error being shown after deployment.

It seems the CDN or Edge routing layer is not connecting to the rendered output despite successful build and aliasing. Vercel edge routing issue?

Can anyone help resolve this?

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.

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.