Heroku H14 No Web Dynos Running

How to fix it

Try these in order — the most common fix is first.

1. 1. Scale the web dyno up

   Copy steps
   1. Run heroku ps:scale web=1 -a <app>
   2. Run heroku ps to confirm it is up
   Did this fix it? Yes No

2. 2. Fix the Procfile

   Copy steps
   1. File must be named Procfile (capital P, no extension) in the repo root
   2. Contains a line like web: gunicorn app:app
   3. Commit and redeploy
   Did this fix it? Yes No

3. 3. Check dyno hours and billing

   Copy steps
   1. Open the Heroku dashboard billing page and check Eco dyno hours
   2. Confirm a payment method is on file
   Did this fix it? Yes No

Symptoms

Logs show code=H14 desc="No web processes running"; site returns 503.

Why it happens

• Web dyno scaled to 0
• Procfile has no web process type or is misnamed
• New app with no process formation after deploy
• Eco dyno hours used up (H82)

This guide also covers

• heroku h14 no web dynos running
• heroku no web processes running
• heroku h14 error

Other Heroku errors

• Heroku H10 App Crashed Error
• Heroku H12 Request Timeout Error
• Heroku R14 Memory Quota Exceeded Error
• Heroku Application Error Page
• Heroku Build Failed Error
• Heroku Git Push Rejected / Remote Rejected
• Heroku R10 Boot Timeout / H20 App Boot Timeout
• Heroku Custom Domain SSL Certificate Not Working