Question

failed (111: Connection refused) while connecting to upstream

I am getting failed (111: Connection refused) while connecting to upstream error in my nginx error log file while trying to access the Django app on my droplet. I understand that the issue my be that nginx is not finding gunicorn. I tried to start gunicorn but getting “start: Unknown job: gunicorn” error, I even tried restarting the droplet but still getting the gunicorn “unknown gunicorn”.

There is also nothing getting printed in my gunicon.log file. I also tried the solutions on similar posts on DO but nothing works

Any help will be highly appreciated, been having this issue for two days with no clue


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Accepted Answer

@hansen I managed to find the solution, it seems like it was timing out, I set --timeout parameter to 120 and it works now. Thank you once again for all the insights provided.

It led to the solution.

@hansen, thank you very much for all the help, I am trying to start the gunicorn service and getting am getting this error

start: Job failed to start

and even if I try to run restart I get

stop: Unknown instance: 
start: Job failed to start

I am suspecting that gunicorn is not started, not sure what to do, I even restarted the droplet but still getting the same error. Sorry again for all these questions it is my first time deploying a Django app.

When launching Gunicorn, try adding the parameter --log-level debug which should add debug to log. Make sure you haven’t change the path to the log file to somewhere else in gunicorn.conf