Platform
Next.js fixes
Next.js errors that survive the deploy: hydration, env vars, and server routes.
13 fixes, most common first.
- Rank 7. Stripe webhook failing: 404, 307/308 redirect, timeout or 500
Stripe shows webhook deliveries Failed with 3xx, 4xx, 5xx or timed out? Point it at the exact final URL and respond 200 fast.
- Rank 22. 500: INTERNAL_SERVER_ERROR / FUNCTION_INVOCATION_FAILED on Vercel
Live site shows 500 FUNCTION_INVOCATION_FAILED but works locally? Your server code crashed. Read the runtime logs, then check env vars.
- Rank 24. Hydration failed because the server rendered HTML didn't match the client
Next.js "Hydration failed" error? The server and browser drew different HTML. Fix nesting, window/localStorage use and dates.
- Rank 33. ReferenceError: window is not defined
Next.js crashes with window is not defined? The page is rendered on the server, where window does not exist. Read it after the component mounts.
- Rank 35. Clerk sign-in keeps redirecting in a loop
The app bounces between the page and Clerk sign-in forever? The redirect target is protected too, or the force-redirect URL points back at the gate.
- Rank 39. Prisma on Vercel: query engine not found
Vercel runs the app and Prisma can't find its query engine? The Rust engine file was left out of the serverless bundle, or Prisma Client was generated for the wrong machine.
Can't fix it? Get help.
If the steps didn't clear the error, send what the screen says. A person can take a look. This is a request for a paid fix, not an instant chat.