128 reputation
26
bio website twitter.com/vjk2005
location Coimbatore, India
age 31
visits member for 3 years, 6 months
seen Mar 3 '13 at 15:52

I design and develop web apps and Chrome extensions. Tools of choice are Node+Mongo for the server-side and standard JS/Jquery for the client-side.


Oct
21
awarded  Notable Question
Jun
29
awarded  Autobiographer
Jan
19
awarded  Notable Question
Sep
20
awarded  Popular Question
May
9
awarded  Student
Feb
16
awarded  Popular Question
Dec
18
awarded  Scholar
Dec
18
accepted “ImportError: No module named flask” - Trouble with nginx + uWSGI + Flask in a virtualenv setup
Nov
30
asked “ImportError: No module named flask” - Trouble with nginx + uWSGI + Flask in a virtualenv setup
Jun
5
comment Nginx + uWSGI on localhost *always* gives 502 Bad Gateway. Any ideas how to solve this?
I just did another round of the internet to see if I can find something useful but haven't turned up anything yet. The basic localhost works, like I mentioned in the post - it says "welcome to nginx". But when I add the uWSGI stuff (I'm not using fastcgi) to the nginx.conf, things turn bad. I logged the uWSGI, made an error on purpose to see if the error was getting logged (which it did) & then ran uWSGI as usual after cleaning up the log - still nothing. Can't wait to see my apps running on my own server. Gonna run out into the webs & search some more. Thanks for all your suggestions & tips.
Jun
5
comment Nginx + uWSGI on localhost *always* gives 502 Bad Gateway. Any ideas how to solve this?
Still no luck. Thanks for the tip about the blocks.
Jun
5
comment Nginx + uWSGI on localhost *always* gives 502 Bad Gateway. Any ideas how to solve this?
Still nothing in the error log. How do I move the log to a higher block?
Jun
5
awarded  Editor
Jun
5
revised Nginx + uWSGI on localhost *always* gives 502 Bad Gateway. Any ideas how to solve this?
added 19 characters in body; added 2 characters in body; added 1 characters in body
Jun
5
comment Nginx + uWSGI on localhost *always* gives 502 Bad Gateway. Any ideas how to solve this?
Ah, thanks for the tip. Left the trailing slash out as browsers auto-add the slash in when going to localhost. Added it back in now.
Jun
5
comment Nginx + uWSGI on localhost *always* gives 502 Bad Gateway. Any ideas how to solve this?
That's on purpose as I recall from SO that new users can't post more than 1 link. Deleted a / so SF didn't auto-detect and add a second link, and then prompt me that new users can't post more than 1 link.
Jun
5
asked Nginx + uWSGI on localhost *always* gives 502 Bad Gateway. Any ideas how to solve this?