Problem with deploying a mezzanine project to VPS

I am trying to deploy a mezzanine instance to my droplet after following the available tutorials and articles available on this site and the Mezzanine docs. I am trying to use nginx with gunicorn along with the mezzanine setup. Everything seems to go well and I deployed using the included However, whenever I run the site, I get the following errors

2016/03/13 05:52:46 [crit] 4516#0: *2 connect() to unix:/home/oilwatch/mezzanine/oilwatch/gunicorn.sock failed (2: No such file or directory) while connecting to upstream, client:, server:, request: "GET / HTTP/1.1", upstream: "http://unix:/home/oilwatch/mezzanine/oilwatch/gunicorn.sock:/", host: ""

I’ve googled around to find a solution but nothing comes close. Has anyone else encountered this and got a solution? I dont know what else to do.

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

That error likely means that Gunicorn isn’t running, and the sock file needed for connection is thus not being created. You’ll likely find the cause in the Gunicorn logs, which you need to set by running Gunicorn with a log file directive like so:

gunicorn -b --access-logfile /var/log/yourapp/gunicorn-access.log --error-logfile /var/log/yourapp/gunicorn-error.log

This will give you even more information about setting log levels: