Deployment Failing without error

[iamshujasaqib]

I have been trying to deploy my changes on production but it keeps failing without any error. I have tried vercel build as well. The build is always successful but in the very end is says An unexpected error happened when running this build. We have been notified of the problem. This may be a transient error. If the problem persists, please contact Vercel Support https://vercel.com/help

Vercel Logs:
16:26:46.412 Running build in Washington, D.C., USA (East) – iad1
16:26:46.421 Build machine configuration: 2 cores, 8 GB
16:26:46.491 Retrieving list of deployment files…
16:26:47.221 Downloading 122 deployment files…
16:26:49.142 Restored build cache from previous deployment (FgWgx8x4SzZKP6v4YaoCJCqMut3B)
16:26:49.530 Running “vercel build”
16:26:49.916 Vercel CLI 48.2.9
16:26:50.289 Installing dependencies…
16:26:51.297
16:26:51.298 added 2 packages in 894ms
16:26:51.298
16:26:51.299 39 packages are looking for funding
16:26:51.299 run npm fund for details
16:26:51.310 Detected Next.js version: 14.2.7
16:26:51.314 Running “npm run build”
16:26:51.437
16:26:51.438 > casino24@0.1.0 build
16:26:51.438 > next build
16:26:51.438
16:26:52.173 ▲ Next.js 14.2.7
16:26:52.174 - Environments: .env
16:26:52.175
16:26:52.193 Creating an optimized production build …
16:27:19.473 Browserslist: caniuse-lite is outdated. Please run:
16:27:19.473 npx update-browserslist-db@latest
16:27:19.473 Why you should do it regularly: GitHub - browserslist/update-db: CLI tool to update caniuse-lite to refresh target browsers from Browserslist config
16:27:21.811 ✓ Compiled successfully
16:27:21.813 Linting and checking validity of types …
16:27:29.004 Collecting page data …
16:27:30.779 Generating static pages (0/31) …
16:27:32.456 Generating static pages (7/31)
16:27:34.273 Generating static pages (15/31)
16:27:34.910 Generating static pages (23/31)
16:27:35.234 ✓ Generating static pages (31/31)
16:27:35.436 Finalizing page optimization …
16:27:35.436 Collecting build traces …
16:27:37.857
16:27:37.868 Route (app) Size First Load JS
16:27:37.869 ┌ ○ / 6.31 kB 130 kB
16:27:37.869 ├ ○ /_not-found 876 B 88.2 kB
16:27:37.870 ├ ○ /404 294 B 94.4 kB
16:27:37.870 ├ ○ /about-us 3.44 kB 116 kB
16:27:37.870 ├ ƒ /blog/[slug] 2.8 kB 123 kB
16:27:37.870 ├ ○ /blogs 3.09 kB 129 kB
16:27:37.871 ├ ○ /bonuses 2.17 kB 122 kB
16:27:37.871 ├ ○ /casinos 2.07 kB 131 kB
16:27:37.871 ├ ○ /details 4.7 kB 125 kB
16:27:37.871 ├ ○ /games 2.26 kB 123 kB
16:27:37.871 ├ ○ /imprint 2.09 kB 114 kB
16:27:37.872 ├ ○ /play-responsibly 4.06 kB 116 kB
16:27:37.872 ├ ○ /sports-betting 3.46 kB 130 kB
16:27:37.872 ├ ○ /terms-and-conditions 4.33 kB 116 kB
16:27:37.873 ├ ○ /vips 352 B 87.7 kB
16:27:37.873 ├ ○ /vips/add-edit-blog 15.8 kB 119 kB
16:27:37.873 ├ ○ /vips/add-edit-bonus 5.62 kB 109 kB
16:27:37.873 ├ ○ /vips/add-edit-casino 4.36 kB 120 kB
16:27:37.874 ├ ○ /vips/add-edit-exclusive-deal 32.1 kB 148 kB
16:27:37.874 ├ ○ /vips/add-edit-game 5.49 kB 109 kB
16:27:37.874 ├ ○ /vips/add-edit-sport 4.43 kB 120 kB
16:27:37.874 ├ ○ /vips/auth 5.12 kB 104 kB
16:27:37.875 ├ ○ /vips/blogs-list 6.74 kB 110 kB
16:27:37.875 ├ ○ /vips/bonuses-list 4.77 kB 108 kB
16:27:37.875 ├ ○ /vips/casinos-list 5.77 kB 109 kB
16:27:37.875 ├ ○ /vips/exclusive-deals-list 4.87 kB 108 kB
16:27:37.876 ├ ○ /vips/games-list 4.88 kB 108 kB
16:27:37.876 ├ ○ /vips/mainpage 76 kB 168 kB
16:27:37.876 ├ ○ /vips/settings 4.57 kB 108 kB
16:27:37.877 └ ○ /vips/sports-list 5.76 kB 109 kB
16:27:37.877 + First Load JS shared by all 87.4 kB
16:27:37.877 ├ chunks/7023-64d7d1cf57d78cc4.js 31.6 kB
16:27:37.877 ├ chunks/fd9d1056-356287bdcf1f524a.js 53.6 kB
16:27:37.883 └ other shared chunks (total) 2.16 kB
16:27:37.883
16:27:37.883
16:27:37.883 ○ (Static) prerendered as static content
16:27:37.883 ƒ (Dynamic) server-rendered on demand
16:27:37.883
16:27:38.014 Traced Next.js server files in: 33.659ms
16:27:38.182 Created all serverless functions in: 168.324ms
16:27:38.200 Collected static files (public/, static/, .next/static): 10.722ms
16:27:38.356 Build Completed in /vercel/output [48s]
16:27:38.543 Deploying outputs…
16:28:14.186 An unexpected error happened when running this build. We have been notified of the problem. This may be a transient error. If the problem persists, please contact Vercel Support https://vercel.com/help

[system]

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.

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 many possible causes, and the absence of something can be tricky debug if you don’t know where to look. Here are some things you can do to find the cause and fix it. Debugging Tips Check the error code If you see a mostly white screen with 404: NOT_FOUND along with a Code and and ID then you can click the blue info box below the error deta…

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