title: gunicorn.socket: Failed with result 'service-start-limit-hit'
body: <p>I was deploying a django app and it failed because for some reason the gunicorn.socket file was not created even though before adding nginx it worked perfectly fine so I searched the internet and found this <a href="https://www.digitalocean.com/community/questions/setting-up-gunicorn-for-django-project-203-exec" rel="noreferrer">answer</a> where the guy says that the reason for this is the virtual environment but I'm sure there must be a way around it using venv right?</p>
  
  <p>the log I get from nginx: </p>
  
  <blockquote>
    <p>connect() to unix:/run/gunicorn.sock failed (11               1: Connection refused) while connecting to upstream, </p>
  </blockquote>
  
  <p>error from gunicorn:</p>
  
  <blockquote>
    <p>gunicorn.socket: Failed with result 'service-start-limit-hit'.</p>
  </blockquote>
  
  <p>I'm 100% sure the problem is with gunicorn not with the setup of nginx becuase I did check for the gunicorn file and it did not exist.</p>