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.
Accepted Answer
@kamstan6 I think you need to set the environment variable SECRET_KEY into the project, since it won’t have access to OS variables, when being executed with upstart. http://stackoverflow.com/questions/30769075/secret-key-error-with-django-using-uwsgi
Hi @kamstan6
Have you checked if upstart script does exactly the same as your command line?
You can find all upstart stuff in /etc/init/ and /etc/init.d/
Sounds to me that it might have something to do with port numbers or maybe the PID file.
Since you’re having problems directly with Gunicorn, then focus on that. It’s not a problem in Nginx until you’re successfully running Gunicorn.
How do you run Gunicorn command vs upstart?