Hello!

On Wed, Jan 08, 2014 at 08:15:47PM -0500, Denis Papathanasiou wrote:

> I've installed nginx via apt, using the nginx stable pkg as described here:
> http://nginx.org/en/linux_packages.html#stable
>
> It works perfectly for serving static files using the default configuration.
>
> Next, I installed uwsgi from source, as described here:
> https://pypi.python.org/pypi/uWSGI/1.2.3
>
> When I do the steps in the python quickstart guide --
> http://uwsgi-docs.readthedocs.org/en/latest/WSGIquickstart.html -- and open
> my browser to localhost:9090, everything works as expected.
>
> When I change the nginx config file to use uwsgi_pass to localhost:9090 as
> described here --
> http://uwsgi-docs.readthedocs.org/en/latest/WSGIquickstart.html#putting-behind-a-full-webserver--
> however, I get time out errors:
>
> > upstream timed out (110: Connection timed out) while reading response
> header from upstream
>
> It is as though nginx is *not* passing those requests to the uwsgi process
> (which is still running).
>
> Here is the content of server{ } inside the nginx config file:
>
> location / {
> include uwsgi_params;
> uwsgi_pass localhost:9090;
> }
>
> Any ideas on what the problem might be?

If you are able to connect to localhost:9090 with your browser,
you are likely using native HTTP support in your uWSGI server.
The "uwsgi_pass" directive assumes uwsgi protocol though, which is
different.

You should either reconfigure uWSGI server to work via uwsgi, or
instruct nginx to talk via HTTP (i.e., use "proxy_pass" instead of
"uwsgi_pass").

--
Maxim Dounin
http://nginx.org/

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx