Next.js dev server stops immediately when opening localhost in browser (no errors)
Answered
Cape lion posted this in #help-forum
Cape lionOP
Hi everyone, I’m stuck with a strange local dev issue in a Next.js 16.0.7 project.
When I run the dev server, I see:
Everything looks normal, but as soon as I open http://localhost:3000 in Chrome, the Next.js dev server immediately stops. No errors, no logs, the process just exits.
Environment:
- Windows 11
- Next.js 16.0.7 (Turbopack)
- Chrome browser
- Astrill VPN (Stealth mode)
Tried:
- Deleting .next folder
- Switching browsers
- Changing dev port
- Excluding browser from Astrill app filter
- Running without extensions
- Reinstalling node_modules
Still the same: opening the page kills the server.
Has anyone experienced this or know how to debug why the Next dev server shuts down with no error? Any help appreciated!
When I run the dev server, I see:
next dev
▲ Next.js 16.0.7 (Turbopack)
- Local: http://localhost:3000
- Network: http://198.18.12.81:3000
✓ Starting...
✓ Ready in 983ms
Everything looks normal, but as soon as I open http://localhost:3000 in Chrome, the Next.js dev server immediately stops. No errors, no logs, the process just exits.
Environment:
- Windows 11
- Next.js 16.0.7 (Turbopack)
- Chrome browser
- Astrill VPN (Stealth mode)
Tried:
- Deleting .next folder
- Switching browsers
- Changing dev port
- Excluding browser from Astrill app filter
- Running without extensions
- Reinstalling node_modules
Still the same: opening the page kills the server.
Has anyone experienced this or know how to debug why the Next dev server shuts down with no error? Any help appreciated!
Answered by Cape lion
I found the issue. It seems to be related to the specific version of Next.js I was using. After downgrading from Next.js 16.0.7 to 15.5.7, the dev server stopped crashing and everything worked normally again.
If anyone runs into a case where the Next.js 16 dev server closes immediately when opening localhost, try using Next 15. That fixed it for me.
Marking this as solved.
If anyone runs into a case where the Next.js 16 dev server closes immediately when opening localhost, try using Next 15. That fixed it for me.
Marking this as solved.
1 Reply
Cape lionOP
I found the issue. It seems to be related to the specific version of Next.js I was using. After downgrading from Next.js 16.0.7 to 15.5.7, the dev server stopped crashing and everything worked normally again.
If anyone runs into a case where the Next.js 16 dev server closes immediately when opening localhost, try using Next 15. That fixed it for me.
Marking this as solved.
If anyone runs into a case where the Next.js 16 dev server closes immediately when opening localhost, try using Next 15. That fixed it for me.
Marking this as solved.
Answer