Flask install 502 Bad Gateway nginx

I am beginner in python development and I first time tried to upload to server DigitalOcean. I followed this tutorial link. But I have a problem when I finished tutorial 502 Bad Gateway nginx/1.10.0 (Ubuntu)


module = wsgi:app

master = true

socket = zlty.sock
chmod-socket = 660
vacuum = true

die-on-term = true


Description=uWSGI instance to serve zlty

ExecStart=/home/dendis/zlty/zltyenv/bin/uwsgi --ini zlty.ini



server {
    listen 80;

    location / {
        include uwsgi_params;
        uwsgi_pass unix:/home/dendis/zlty/zlty.sock;

Log in nginx 2016/07/26 03:53:02 [crit] 9563#9563: *9 connect() to unix:/home/dendis/zlty/zlty.sock failed (2: No such file or directory) while connecting to upstream, client:, server:, request: "GET / HTTP/1.1", upstream: "uwsgi://unix:/home/dendis/zlty/zlty.sock:", host: ""

Show comments

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.


   ``` uwsgi_pass unix:/home/jrm2k6/jeremydagorn-blog/jeremydagorn.sock;```


   ```uwsgi_pass unix:///home/jrm2k6/jeremydagorn-blog/jeremydagorn.sock;```

and restart Nginx. It might help you.

OR refer -

When following this tutorial did you complete the section on creating and testing a sample application. This section included temporarily opening port 5000 and ensuring the app is returned. It sounds like the flask application itself is not responding when it is requested by nginx upstream so working from the bottom of the stack should be the best way to identify the issue.