Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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!
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.
I had a similar problem, and all logs were empty too !!
The problem with me was that I’m using environment variables in code, that was declared in .bashrc but wasn’t read ! The solution was to declare those environment variable inside /etc/init/gunicorn.conf file.
env KEY=VALUE
And it works :) This may help you, or if not check init files reference It may be more useful
The errors mean that whatever should be running on port 9000 isn’t running, which is gunicorn in this case.
Check gunicorn’s error log, are there any errors?
sudo tail -30 /var/log/upstart/gunicorn.log
Unrelated: I would replace --bind=0.0.0.0:9000 with --bind=127.0.0.1:9000 so that gunicorn itself can’t be accessed externally (you want everything to go through nginx first).