@Carlos Hi Can you send me your working production.ini and nginx.conf files. I will compare mine and try to find the issues with my conf files. Thanks in advance.
On Tuesday, 26 June 2012 20:35:30 UTC+5:30, jeetu wrote: > > Now I am trying with tcp socket in uwsgi. Still no success. > > new production.ini -> http://pastebin.com/CqwNfqYQ > new gmatweb_nginx.conf -> http://pastebin.com/J6G0gy2u > > But I am able to serve it directly using uwsgi --http 127.0.0.1:8090--ini > production.ini > > On Tuesday, 26 June 2012 13:25:08 UTC+5:30, Carlos Daniel Ruvalcaba > Valenzuela wrote: >> >> Perhaps is the socket path that is causing you problem, in an example >> app I have the following line on nginx config: >> >> >> location / { >> include uwsgi_params; >> uwsgi_pass unix:/tmp/acatalog.sock; >> } >> >> As I see on your pasted files there are too many slashes ( / ), try >> with just one root slash. >> >> If you are using virtualenv don't forget to tell uwsgi about it, there >> is many aliases, pythonpath, virtualenv, pp, etc. >> >> Regards, >> Carlos Daniel Ruvalcaba Valenzuela >> > -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To view this discussion on the web visit https://groups.google.com/d/msg/turbogears/-/kYGWW2k2-jUJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
