uwsgi problems

[Greg Barker]

Option #2 should work, here's what I have for my uwsgi site. Double check
your permissions on the directory the uwsgi.sock lives in.

My nginx conf:
location / {
    uwsgi_pass unix:///var/www/my_app/my_virtualenv/run/uwsgi.sock;
    include uwsgi_params;
}


Directory permissions:
$ ls -la /var/www/my_app/my_virtualenv/run/
total 12
drwxr-xr-x 2 www-data www-data 4096 Sep 29 13:03 .
drwxr-xr-x 7 www-data www-data 4096 Jul 22 23:05 ..
srwxr-xr-x 1 www-data www-data    0 Sep 29 13:03 uwsgi.sock

My vassal contains:
[uwsgi]
socket = /var/www/my_app/my_virtualenv/run/uwsgi.sock
uid = www-data
gid = www-data

On Thu, Oct 9, 2014 at 5:45 AM, Steven Williams <
theblessedadventhope at gmail.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have been trying to get nginx to talk to uwsgi to no avail. uwsgi
> works by itself as I can host it on port 80 on my local machine with no
> problems. I have tried configuring nginx with the following variations:
>
> # option 1
> location / {
>     include uwsgi_params;
>     uwsgi_pass unix:/tmp/uwsgi.sock;
> }
>
> # option 2
> location / {
>     include uwsgi_params;
>     uwsgi_pass unix:///tmp/uwsgi.sock;
> }
>
> # option 3
> location / {
>     include uwsgi_params;
>     uwsgi_pass 127.0.0.1:3000;
> }
>
> These are the corresponding errors I get:
>
> # option 1
>
> # option 2
> 2014/10/08 14:24:39 [crit] 15736#0: *8 connect() to
> unix:///tmp/uwsgi.sock failed (2: No such file or directory) while
> connecting to upstream, client: 127.0.0.1, server: localhost, request:
> "GET / HTTP/1.1", upstream: "uwsgi://unix:///tmp/uwsgi.sock:", host:
> "127.0.0.1"
>
> # option 3
>
>
> - --
> Steven Williams
> My PGP Key: http://pgp.mit.edu/pks/lookup?op=get&search=0xCACA6C74669A54FA
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQIcBAEBAgAGBQJUNoNoAAoJEMrKbHRmmlT6pWkP/i5w/RJdEKOS9C22W6WxIbmr
> MjrTH4L0FwrCizZnI+dV+2XnYSEkky4GzefaoffpoWsr/sfA7UwMYfjSiYrWcxxE
> 3U4mbyJVpxiJmafVswoifKJspHTGtsFDwigm0/k04TTml8exPK9sjLUFF4I/um7H
> CzEOvHahC1GIaeEWl+38GZAmSnBNo99TGSpQKzWaZ9zw5hed+ySkVj/nMIijNp0Y
> euLOKuH93JzSgRAY54fxVd8J+mLRh+HX/NUfAkEoDtJ2Bq6ltcgTmy4Q5HHTwrxP
> 8ekQk1Pmea7SMFiAU/zkD4WVTp3tyXX5F31DtTXXzGKVTt0VJZBbmXK1AwIO8H9h
> RyVyg10T5+4PCPWSpn7SLtAgdDupb7YXTXP4Owov7P47bawy6+z+9LaE5/IWc8V7
> DY477LLmnbYK0M8voJcgcIVLWsS65yTr8l7S6tXBI8ONRmiPvr33MInGy14JefCv
> fXCkeCOYCwa6dVGLFHMHpDLcSWzxPPCSMjHyTOu2KpTpjwJO7qGpoZVXlrKt+Qkq
> JeFCAhbSAsPI1v8dcf5JzXXz1bjnOKhSVWQFgYg+MTqNoWq3oG1JLhuO19VR4Wb/
> Kol91PhT6FkQITMWeBNftMqzatuk1sD5vXxl8kgycJTFCbtys64DKGgBmpkyfa56
> 2z62sKR23yH7VJuu4knb
> =9laf
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20141009/3fcff3b0/attachment.html>