Time out errors using uwsgi with ngnix on debian 7 (wheezy)

Denis Papathanasiou denis.papathanasiou at gmail.com
Thu Jan 9 17:08:23 UTC 2014


Thank you for your reply.

On Thu, Jan 9, 2014 at 10:03 AM, Maxim Dounin <mdounin at mdounin.ru> wrote:

> [snip]
> If you are able to connect to localhost:9090 with your browser,
> you are likely using native HTTP support in your uWSGI server.

Yes, I am starting the uwsgi process like this, using the --http flag:

uwsgi --http :9090 --wsgi-file foobar.py --master --processes 4 --threads 2

> The "uwsgi_pass" directive assumes uwsgi protocol though, which is
> different.
> You should either reconfigure uWSGI server to work via uwsgi, or

Ah, I see, I should use the --socket option instead, like this:

uwsgi --socket --wsgi-file foobar.py --master --processes 4
--threads 2

Thank you for clarifying that; it *is* in the uwsgi docs I quoted earlier,
but it is a subtle point under the "quickstart" section, and I had missed

> instruct nginx to talk via HTTP (i.e., use "proxy_pass" instead of
> "uwsgi_pass").

I see: I could use "proxy_pass" and keep --http  when I start uwsgi.

Thank you, that was very helpful!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140109/f1b46648/attachment.html>

More information about the nginx mailing list