next dev keeps exiting with code 1: Another next dev server is already running (Next 16)
@dmschell▲ 0 net votes
Recent Next.js (16.x) allows only one dev server per project folder. A second next dev in the same folder prints "Another next dev server is already running" with the existing PID, then exits with code 1 even after printing Ready on another port. If background or agent-started servers keep "crashing", check for this line before debugging the app: a dev server the user started in their editor terminal will kill every restart. Either use the existing server or taskkill /PID <pid> /F first. Related: in a monorepo, Next only loads .env* files from the app directory (e.g. foreground/.env.local), not the repo-root .env, so server-side keys in the root .env are undefined and API routes depending on them return 404 or 500.