nodemon crashed Node.js Origin: Application & API OSI layer 7 · Application Last updated 15 Oct 2026

[nodemon] app crashed - waiting for file changes before starting...

Your app threw an error on startup; nodemon is waiting for a file change to retry.

Exact message you may see app crashed - waiting for file changes before starting[nodemon] app crashed
Seen on: Node.js

Meaning

The message is only nodemon’s status — the real error is printed just above it.

Common causes

  • Startup exception (syntax error, missing module)
  • Port already in use
  • Missing environment variable or config file

⚡ Quick fix

  1. Scroll up to the first error above this line
  2. Fix it and save a file to restart
  3. Run node directly to see output without nodemon

Detailed fix by platform

Node.js

  1. node --trace-uncaught src/index.js

How to diagnose

  1. Error above — What was printed before the crash line?
  2. Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Application & API. Errors that are often confused with or caused by this one (click to open):

500.30 — HTTP Error 500.30 - ASP.NET Core app failed to start (.NET)500.30AH00015: Unable to open logs — Apache: AH00091: apache2: could not open error log file /var/log/apache2/error.log. AH00015: Unable to open logs (Permission denied) (Nginx / Apache)AH00015: Unable to op…AH00072: make_sock: could not bind to address 0.0.0.0:80 — Apache: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80 / AH00015: Unable to open logs (Nginx / Apache)AH00072: make_sock: c…AH00112: DocumentRoot does not exist — Apache: AH00112: Warning: DocumentRoot [/var/www/example.com/public_html] does not exist (Nginx / Apache)AH00112: DocumentRoot…EADDRINUSE — Error: listen EADDRINUSE: address already in use :::3000 (Node.js)EADDRINUSEExceptionInInitializerError — java.lang.ExceptionInInitializerError (Java)ExceptionInInitialize…exit(1) — Cloud Run: Container called exit(1) — the revision failed to start (Google Cloud / Firebase)exit(1)Exited (0) — Docker container exits immediately (Exited (0) / Exited (1) right after start) (Docker)Exited (0)nodemon c…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.