Flask + uwsgi + nginx + debug. 502 error instead of debugger page

Question

Run Flask on server with uWsgi.

uWsgi config

<uwsgi>
    <socket>/tmp/flask.sock</socket>
    <pythonpath>/home/reweb/flask/</pythonpath>
    <module>publicist:app</module>
    <plugins>python27</plugins>
    <uid>reweb</uid>
   <touch-reload>/home/reweb/reload</touch-reload>
</uwsgi>

nginx config

upstream flask_serv {
    server unix:/tmp/flask.sock;
}

server {
    listen 80;
    server_name some-domain.com;

    access_log /home/reweb/log/nginx-access.log;
    error_log /home/reweb/log/nginx-error.log;

    location / {
        uwsgi_pass flask_serv;
        include uwsgi_params;
    }
}

But instead of debugger page nginx show me 502 error.
All Flask error traceback i can see in uwsgi error log.

UPDATE
Find old question nginx + uwsgi + flask - disabling custom error pages there is no answer

possible duplicate of [Flask debug=True does not work when going through uWSGI](http://stackoverflow.com/questions/10364854/flask-debug-true-does-not-work-when-going-through-uwsgi) — Daniel Fairhead, Nov 21 '13 at 10:36

score 3 · Accepted Answer · edited May 23 '17 at 11:44

3

All you need to know:

https://stackoverflow.com/a/10460399/814470
https://stackoverflow.com/a/17839750/814470

Two answers from duplicated question

edited May 23 '17 at 11:44

Community

1
1

answered Dec 10 '14 at 11:26

Jafte

93
12

score 1 · Answer 2 · edited May 23 '17 at 10:28

1

Flask debug=True does not work when going through uWSGI

may help. Essentially, uwsgi is not intended for development environments where you want debugging info in the browser. It's a production server.

possibly adding in app.debug = true may help, after you have instantiated the Flask object, but otherwise, to get a proper debugger, use the flask internal server for development.

edited May 23 '17 at 10:28

Community

1
1

answered Nov 21 '13 at 10:35

Daniel Fairhead

1,103
9
9

Flask + uwsgi + nginx + debug. 502 error instead of debugger page

2 Answers2