What is probably broken
The build passes locally, but the server has missing env vars, a dead Node process, or Nginx pointing at the wrong port.
The build passes locally, but the server has missing env vars, a dead Node process, or Nginx pointing at the wrong port.
A live Next.js app on your domain, served behind Nginx with HTTPS and a deployment path you can repeat.
STEP 01
Start by making the app build cleanly with production env vars present. Most broken deploys are not server problems, they are hidden build assumptions.
STEP 02
A VPS does not keep your app alive automatically. Use a process manager so deploys and restarts are predictable.
STEP 03
Nginx handles public traffic, TLS, compression, and proxying to the private Node port.
Quick check
If you cannot tick all five, we can fix it. Send us the repo and we handle the rest.
Free checklist
Get the exact 5-step checklist we run before every deploy. No fluff, just the things that actually break.
Done-for-you deploy
Fixed price per repo. 24h delivery or full refund. No hourly billing.
Related guides
Diagnose and fix Nginx 502 errors by checking upstream ports, app process health, proxy config, firewall rules, and runtime logs.
Read guideHit serverless limits or seat pricing on Vercel? Move your AI-built app to a VPS for lower costs, long-running jobs, and full control. Step-by-step migration guide.
Read guidev0-generated apps need a repo, env vars, and server process before going live. Move your app from preview to a VPS you own with lower recurring cost.
Read guide