You can't browse to the URL because there is no web application running on port 8009.

You tell nginx to listen on port 80...so far all good.

But then you are telling nginx to proxy_pass the request to a diferent port...
So the question is more: is this really what you want? If so... may I ask what's supposed to be listening on port 8009?

I mean you said before that nothing is listening on port 8009... but you want nginx to proxy the requests to that port... this makes no sense.




imran_kh <nginx-forum@nginx.us> wrote:
>Hello,
>
>Thanks for the reply but when I am browsing example.com or using ip
>address
>getting error " 502 bad gateway".
>Please suggest me on this..
>
>Thanks,
>Imran Khan.
>
>Posted at Nginx Forum:
>http://forum.nginx.org/read.php?2,241157,241160#msg-241160
>
>_______________________________________________
>nginx mailing list
>nginx@nginx.org
>http://mailman.nginx.org/mailman/listinfo/nginx

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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