502 Bad Gateway usually indicates a problem with the application (or
upstream) server. In this case, I think that would be Unicorn. Double
check that Unicorn is configured and running and correctly and that the
port or socket that you have in your nginx config is the same as the
one Unicorn is listening on.

_Nik

On 2/12/2013 12:16 PM, Raghvendra Parashar wrote:
> Hi nginx team,
>
> I am getting 502 bad gateway error for particular URL.
>
> Application details :
> Rails 3.1.0
> Ruby 1.9.2
> unicorn 4.2.0
> resque 1.20.0
> nginx/1.0.14
> redis 2.4.8
>
> nginx error log :|
> 2013/02/1207:36:16[error]32401#0: *1948 upstream prematurely closed
> connection while reading response header from upstream|
>
> I have also posted my question on stack-overflow, please find it here
> http://stackoverflow.com/questions/14825304/502-error-nginx-ruby-on-rails-application,
> but couldn't got any response.
>
> Please guide me to solve this problem.
>
> Thanks
> Regards:
> Raghvendra Kumar Parashar
>
>
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

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