Gunicorn always starts with 1 worker despite configuration
kurdog
PROOP

a month ago

Hi Railway team,

I'm on Pro Plan and my Gunicorn always starts with 1 worker,

despite multiple configuration attempts:

- gunicorn_config.py with workers=4 (hardcoded)

- Procfile: gunicorn main:app -c gunicorn_config.py

- WEB_CONCURRENCY=4

- nixpacks.toml with --workers 4

Logs show: "[INFO] Booting worker with pid: 4" (only 1 worker)

Service ID: [your-service-id]

Expected: 4 workers

Actual: 1 worker

Can you help identify why Railway ignores worker configuration?

Solved$10 Bounty

2 Replies

Railway
BOT

a month ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


Status changed to Awaiting Conductor Response noahd 26 days ago


Can you send your GitHub repository please?


Status changed to Awaiting User Response Railway 25 days ago


Railway
BOT

18 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 18 days ago


Loading...