Not connecting to gunicorn, Gunicorn Exited too quickly – Nginx

Your issue could be a combination of a few things:

1. Verify you django settings.py is set up properly for deployment. Pay very close attention to the STATIC_ROOT and STATICFILES_DIR variables as they are critical to serving your projects static files.

2. Make sure your virtualenv is activated and you have ran pip install -r requirements.txt.

Note: At this point try to run your project with your servers public ip python manage.py runserver server_public_ip:8000 a lot of people assume that, because their project ran locally, it will run on the server. Something always goes wrong.

1. Make sure you run python manage.py collectstatic on your server. This collects your static files and makes a directory for it. Take note of the path it tells you it’s going to copy them to, you’re going to need it for your /static/ location block in your nginx sites-available configuration file.

2. Make sure your gunicorn.conf command variable points to your virtualenv path, and that it points to a .sock file that gunicorn and nginx can access (sudo chown user:group). Here is an example:

    [program:gunicorn]
   
    command=/home/user/.virtualenvs/djangoproject/bin/gunicorn -w3 --bind unix:/etc/supervisor/socks/gunicorn.sock djangoproject.wsgi:application --log-level=info
    directory=/home/user/djangoproject
    numprocs=3
    process_name=%(program_name)s_%(process_num)d
    user=user
    environment=LANG=en_US.UTF-8,LC_ALL=en_US.UTF-8,HOME="/home/user/djangoproject", USER="user" 
   
    autostart=true
    autorestart=true
    stderr_logfile=/var/log/supervisor/gunicorn.err.log
    stdout_logfile=/var/log/supervisor/gunicorn.out.log
   

3. There are a couple ways you can set up your nginx configuration files. Some docs have you do it all in the nginx.conf file, however, you should break it up into sites-available with a symbolic link to sites-enabled. Either way should get you the same result. Here is an example:

   upstream django {
       server unix:/etc/supervisor/socks/gunicorn.sock;
   }
   
   server {
       listen 80;
       server_name www.example.com;
       client_max_body_size 4G;
       proxy_set_header Host $host;
       proxy_set_header X-Forwarded-Proto $scheme;
       proxy_set_header X-Real-IP $remote_addr;
       proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
       proxy_headers_hash_max_size 1024;
       proxy_read_timeout 300s;
       proxy_connect_timeout 75s;
   
       access_log /var/log/nginx/access.log;
       error_log /var/log/nginx/error.log debug;
   
       location /media/ {
           autoindex off;
           alias /home/user/djangoproject/media/;
       }
   
       location /static/ {
           autoindex off;
           alias /home/user/djangoproject/static/;
       }
   
       location / {
           proxy_pass http://django;
           proxy_redirect off;
       }
   }
   

4. Make sure that you run sudo service nginx restart after every nginx configuration change.

5. Make sure you run sudo supervisorctl reread, sudo supervisorctl update all, and sudo supervisorctl restart all after every supervisor configuration file change. In your case every gunicorn.conf file change.

6. Lastly, as a general rule, make sure all of your directory paths match to their respected processes. For example: Let’s say your gunicorn command variable points to a sock file that is in /path/to/project/gunicorn.sock, but your nginx configuration has a proxy_pass to /etc/supervisor/socks/gunicorn.sock, nginx doesn’t know where to pass your requests to, so gunicorn never sees the request. Also, you can add this to your nginx location blocks so you can see where each request gets to in your browser dev tools response header: add_header X-debug-message "The port 80, / location was served from django" always;

Note: If you are getting the "Welcome to Nginx" page, it means nginx doesn’t know where to send the request. A lot of times you have a static root directory path problem. However, there are other issues, but situational to how things are set up. You’ll have to debug with some trial and error. Also, try adding a location block to a known url like http://example.com/login, if you get there, you know you have an nginx configuration issue. If you get 404 not found, then you most likely have a django project problem or a gunicorn problem.