I figured it out - turns out I had nginx configured to use fastcgi - which is why it (kinda) worked with Flup#fcgi_thread. I reconfigured nginx to just forward requests on to the Paster process running at 127.0.0.1:8989 and it works brilliantly.
Thanks all for readying my post :) cheers On Thursday, 21 March 2013 17:29:05 UTC-4, Jarrett Chisholm wrote: > > hey all, > > I'm trying to setup my test server to use flup. I'm using the tg2 test > app. My production.ini uses it like so: > > ... > ... > [server:main] > #use = egg:Paste#http > use = egg:Flup#fcgi_thread > host = 127.0.0.1 > port = 8989 > ... > ... > > > I start it like so: > sudo paster serve production.ini > > > However, when I navigate to 127.0.0.1:8989, it doesn't connect to > anything (it just sits there). I have nginx setup to forward incoming > requests for mywebsite.com to 127.0.0.1:8989. If I navigate to > mywebsite.com it will actually forward me to the page, however, no > images/css/javascript gets loaded. Also, if I try to navigate to another > part of the site, it can't find the page. > > When i change production.ini to be: > ... > ... > [server:main] > use = egg:Paste#http > host = 127.0.0.1 > port = 8989 > ... > ... > > I can navigate to 127.0.0.1:8989 and it works as expected (and > css/javscript/images all load, and I can navigate properly). However, > navigating to mywebsite.com shows a 502 error... > > > Does anyone have any idea why I might be having these issues when using > flup? I don't necessarily care which one I use, I just need it to work > from both 127.0.0.1 and from mywebsite.com. > > cheers > -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
