Blank screen after deployment

I have a project and it works in the preview but when I deploy I get a blank screen. This is the URL

https://sparkgive.com/

Basically everything on your page has opacity: 0; set, can you check the code (or ask v0) to see what causes that? That should give you the root cause for why it doesnโ€™t work when deployed

Itโ€™s because I have animation fade-in but thatโ€™s not the problem. If you open the console network tab, you will see a bunch of errors. I asked v0 to fix but still no solution. Those errors does not happen during preview though.


See image

Youโ€™ll need to check your server logs โ€“ click the deploy button and โ€œopen in Vercelโ€, then go to the logs for your latest deployment. You should see the 500s there, with details on what happened

Jacob, I think you are misunderstanding. The deploy works fine, the preview works fine. No errors during deployment but when I got to my website either using the vercel link or my domain, thatโ€™s when I get all those errors. See my build log below:

[23:36:14.172] Running build in Washington, D.C., USA (East) โ€“ iad1
[23:36:14.187] Cloning github.com/libinysolutions/spark-give (Branch: main, Commit: ab9dc3a)
[23:36:15.333] Cloning completed: 1.146s
[23:36:17.516] Restored build cache from previous deployment (4iD4wyJUAhE5frM4kjoUrxxQjnBQ)
[23:36:18.176] Running "vercel build"
[23:36:18.563] Vercel CLI 41.6.2
[23:36:18.892] Detected `pnpm-lock.yaml` 9 which may be generated by pnpm@9.x or pnpm@10.x
[23:36:18.892] Using pnpm@10.x based on project creation date
[23:36:18.892] To use pnpm@9.x, manually opt in using corepack (https://vercel.com/docs/deployments/configure-a-build#corepack)
[23:36:18.906] Installing dependencies...
[23:36:19.675] Lockfile is up to date, resolution step is skipped
[23:36:19.771] Already up to date
[23:36:20.147] 
[23:36:20.148] โ•ญ Warning โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
[23:36:20.148] โ”‚                                                                              โ”‚
[23:36:20.148] โ”‚   Ignored build scripts: sharp.                                              โ”‚
[23:36:20.148] โ”‚   Run "pnpm approve-builds" to pick which dependencies should be allowed     โ”‚
[23:36:20.148] โ”‚   to run scripts.                                                            โ”‚
[23:36:20.148] โ”‚                                                                              โ”‚
[23:36:20.148] โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ
[23:36:20.148] 
[23:36:20.171] Done in 1.1s using pnpm v10.9.0
[23:36:20.183] Detected Next.js version: 15.2.4
[23:36:20.195] Running "pnpm run build"
[23:36:20.515] 
[23:36:20.515] > my-v0-project@0.1.0 build /vercel/path0
[23:36:20.515] > next build
[23:36:20.515] 
[23:36:21.216]  โš  Invalid next.config.mjs options detected: 
[23:36:21.216]  โš      Unrecognized key(s) in object: 'optimizeFonts' at "experimental"
[23:36:21.216]  โš      Unrecognized key(s) in object: 'swcMinify'
[23:36:21.217]  โš  See more info here: https://nextjs.org/docs/messages/invalid-next-config
[23:36:21.274]    โ–ฒ Next.js 15.2.4
[23:36:21.274] 
[23:36:21.354]    Creating an optimized production build ...
[23:36:42.616]  โœ“ Compiled successfully
[23:36:42.620]    Skipping validation of types
[23:36:42.620]    Skipping linting
[23:36:42.871]    Collecting page data ...
[23:36:43.405] Attempted to use Supabase client on the server
[23:36:43.422] Attempted to use Supabase client on the server
[23:36:43.505] Attempted to use Supabase client on the server
[23:36:45.533]    Generating static pages (0/19) ...
[23:36:46.103] Attempted to use Supabase client on the server
[23:36:46.430] Attempted to use Supabase client on the server
[23:36:46.430]    Generating static pages (4/19) 
[23:36:46.503]    Generating static pages (9/19) 
[23:36:46.503]    Generating static pages (14/19) 
[23:36:46.503]  โœ“ Generating static pages (19/19)
[23:36:46.824]    Finalizing page optimization ...
[23:36:46.824]    Collecting build traces ...
[23:36:54.495] 
[23:36:54.512] Route (app)                                 Size  First Load JS
[23:36:54.512] โ”Œ โ—‹ /                                    14.1 kB         221 kB
[23:36:54.512] โ”œ โ—‹ /_not-found                            980 B         102 kB
[23:36:54.512] โ”œ โ—‹ /access-denied                         178 B         104 kB
[23:36:54.512] โ”œ ฦ’ /api/stripe/webhook                    169 B         101 kB
[23:36:54.512] โ”œ ฦ’ /api/twilio/sms                        169 B         101 kB
[23:36:54.513] โ”œ โ—‹ /auth-debug                          3.18 kB         147 kB
[23:36:54.513] โ”œ ฦ’ /auth/callback                         169 B         101 kB
[23:36:54.513] โ”œ ฦ’ /church/communications               1.57 kB         226 kB
[23:36:54.513] โ”œ ฦ’ /church/dashboard                      178 B         104 kB
[23:36:54.513] โ”œ ฦ’ /church/donations                      208 B         224 kB
[23:36:54.513] โ”œ ฦ’ /church/events                         169 B         101 kB
[23:36:54.513] โ”œ ฦ’ /church/giving-setup                 11.6 kB         135 kB
[23:36:54.513] โ”œ ฦ’ /church/members                        208 B         224 kB
[23:36:54.513] โ”œ โ—‹ /church/plans-and-pricing            5.58 kB         126 kB
[23:36:54.513] โ”œ ฦ’ /dashboard                             286 B         156 kB
[23:36:54.513] โ”œ โ—‹ /dashboard/campaigns                 3.38 kB         159 kB
[23:36:54.513] โ”œ ฦ’ /dashboard/donations                   280 B         156 kB
[23:36:54.513] โ”œ ฦ’ /dashboard/donors                      280 B         156 kB
[23:36:54.514] โ”œ โ—‹ /dashboard/settings                   3.4 kB         182 kB
[23:36:54.514] โ”œ โ—‹ /debug                               2.63 kB         151 kB
[23:36:54.514] โ”œ โ—‹ /debug/advanced                      4.28 kB         157 kB
[23:36:54.514] โ”œ ฦ’ /donor-dashboard                       186 B         157 kB
[23:36:54.514] โ”œ โ—‹ /donor-dashboard/donations           2.38 kB         159 kB
[23:36:54.514] โ”œ โ—‹ /login                                 156 B         185 kB
[23:36:54.514] โ”œ โ—‹ /register-church                     4.06 kB         179 kB
[23:36:54.514] โ”œ ฦ’ /server-auth-test                      169 B         101 kB
[23:36:54.514] โ”œ ฦ’ /session-test                          169 B         101 kB
[23:36:54.514] โ”œ โ—‹ /signup                                156 B         185 kB
[23:36:54.514] โ”” โ—‹ /signup/verify-email                   187 B         110 kB
[23:36:54.514] + First Load JS shared by all             101 kB
[23:36:54.515]   โ”œ chunks/1acdb12c-ecfd90e11256ea65.js  53.2 kB
[23:36:54.515]   โ”œ chunks/5575-5e1d01ac167c4a74.js        46 kB
[23:36:54.515]   โ”” other shared chunks (total)          1.96 kB
[23:36:54.515] 
[23:36:54.515] 
[23:36:54.515] ฦ’ Middleware                             24.4 kB
[23:36:54.515] 
[23:36:54.515] โ—‹  (Static)   prerendered as static content
[23:36:54.515] ฦ’  (Dynamic)  server-rendered on demand
[23:36:54.515] 
[23:36:54.686] Traced Next.js server files in: 84.215ms
[23:36:54.809] Created all serverless functions in: 122.645ms
[23:36:54.848] Collected static files (public/, static/, .next/static): 7.808ms
[23:36:54.963] Build Completed in /vercel/output [36s]
[23:36:55.047] Deploying outputs...
[23:37:04.500] 
[23:37:04.803] Deployment completed
[23:37:17.164] Uploading build cache [200.34 MB]...
[23:37:21.251] Build cache uploaded: 4.087s

Not the build logs โ€“ the request logs let you see each request and what the server is saying about each 500

500 just means โ€œInternal Server Errorโ€ and thatโ€™s all the information it passes to the client, so the server logs will tell you what actual error underlies it

It looks like requests for your static files are being captured by the server instead, so Iโ€™m guessing there may be middleware thatโ€™s operating too aggressively, but checking these logs should help diagnose that

1 Like

You were right. That was the problem. A middleware somewhere and v0dev fixed. Thank you so much

3 Likes

Amazing, happy it worked!

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