Django: Gunicorn Workers Timing Out
Workers.
Gunicorn kills a worker that does not answer in time and logs WORKER TIMEOUT. The default is 30 seconds, so slow views and heavy tasks trigger it.
Step 1: Read the log

Look for WORKER TIMEOUT and Booting worker lines to see which requests time out.
Step 2: Find the slow code

Check the view for slow queries, external API calls or large file work.
Step 3: Raise the timeout

Start Gunicorn with --timeout 120 for legitimately long requests.
Step 4: Adjust workers

A common start is 2 x CPU cores + 1. Too few workers queue requests, too many exhaust memory.
Step 5: Move heavy work out

Use a task queue such as Celery for emails, reports and imports.
Step 6: Check the proxy

Nginx proxy_read_timeout should be at least the Gunicorn timeout.
Step 7: Restart and monitor

Restart the service and watch memory and response times.
Still stuck?
If these steps do not solve it, we fix it for you for a flat $99. Full refund if we do not solve it within 7 days.
Related guides
- Writing Clear Error Reports: Screenshots, URLs and Steps
- WordPress Tag and Date Archives Duplicate Content: Settings
- WordPress Permalinks Change: Redirect Old URLs and Avoid 404s
- Error Establishing a Database Connection in WordPress: Full Checklist