Re: Not listing proxy_pass port 8009

2013-07-24 Thread naseeb0077
Hello, Thanks for the prompt reply. I have scanned the listing ports in the servers. Please help me out to fix this issue. I never worked on Nginx server and am totally stuck. # sudo nmap localhost Starting Nmap 5.21 ( http://nmap.org ) at 2013-07-23 20:15 EDT Nmap scan report for localhost (127

Re: Not listing proxy_pass port 8009

2013-07-24 Thread Nikolas Stevenson-Molnar
That looks like an OpenERP problem: http://bit.ly/1aJm0DB _Nik On 7/24/2013 1:36 PM, imran_kh wrote: > Hello, > > Thanks for the reply. > > Yes you are correct. I have tried to change the port from 8080 to 80 in > /etc/nginx/conf.d/default.conf. > Browse the Public IP address and xyz.com site, g

Re: Not listing proxy_pass port 8009

2013-07-24 Thread imran_kh
Hello, Any suggestion or advice? Thanks, Imran Khan. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,241157,241207#msg-241207 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Not listing proxy_pass port 8009

2013-07-24 Thread imran_kh
Hello, Thanks for the reply. Yes you are correct. I have tried to change the port from 8080 to 80 in /etc/nginx/conf.d/default.conf. Browse the Public IP address and xyz.com site, getting “no handler found” error. File /etc/nginx/conf.d/default.conf content as follows. # sudo cat default.conf #

Re: Not listing proxy_pass port 8009

2013-07-24 Thread Nikolas Stevenson-Molnar
Go back over all your nginx conf files, making sure to look at included files as well... it seems that somewhere you have "listen 8080" and possibly overlapping "server_name" directives. If that fails, I'd suggest you backup then throw out your current config, then start simple and build it up one

Re: Not listing proxy_pass port 8009

2013-07-24 Thread imran_kh
Hello, I have observed that, Nginx configured on port 80 as per /etc/nginx/sites-enabled/default file but it is listening on port 8080 and 80. Please see the details for the same. server { listen 80; server_name example.com; location / { proxy_pass http://localhost:8009; send_timeout 6000; proxy

Re: Not listing proxy_pass port 8009

2013-07-23 Thread Nikolas Stevenson-Molnar
Are there supposed to be services running on ports 8002 and 8007? If so, then they don't seem to actually be running and you need to fix that (that's not nginx-related). If you actually meant to proxy to another port(s), then look at your nginx config, find where you're proxying to 8002 and 8007 an

Re: Not listing proxy_pass port 8009

2013-07-23 Thread imran_kh
Hello, Thanks but how can I resolve the error “502 bad gateway” for IP Address? Getting this error while browsing site using IP Address. Thanks. Imran khan, Posted at Nginx Forum: http://forum.nginx.org/read.php?2,241157,241177#msg-241177 ___ nginx m

Re: Not listing proxy_pass port 8009

2013-07-23 Thread Nikolas Stevenson-Molnar
If 8009 is the desired port, then change the upstream server in your nginx conf to use port 8009. If 8002/8007 are the correct ports, then change the upstream server to listen on those ports. _Nik On 7/23/2013 5:44 PM, imran_kh wrote: > Hello, > > Correct. So how should I resolve this issue? > >

Re: Not listing proxy_pass port 8009

2013-07-23 Thread imran_kh
Hello, Correct. So how should I resolve this issue? Thanks, Imran Khan. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,241157,241175#msg-241175 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Not listing proxy_pass port 8009

2013-07-23 Thread Nikolas Stevenson-Molnar
Note that the log entries from your previous email indicate upstream servers on ports 8002 and 8007. According to what you've posted here, there's nothing listening on either of those ports. _Nik On 7/23/2013 5:20 PM, imran_kh wrote: > Hello, > > Thanks for the prompt reply. > > I have scanned th

Re: Not listing proxy_pass port 8009

2013-07-23 Thread imran_kh
Hello, Thanks for the prompt reply. I have scanned the listing ports in the servers. Please help me out to fix this issue. I never worked on Nginx server and am totally stuck. # sudo nmap localhost Starting Nmap 5.21 ( http://nmap.org ) at 2013-07-23 20:15 EDT Nmap scan report for localhost (12

Re: Not listing proxy_pass port 8009

2013-07-23 Thread Miguel C.
The log tells you much... although has was already said the problem is that something's wrong with whatever should be listening on those ports... Openerp is one of those and probably is not running or at least it's not listening on the port specified in nginx configuration... In any case the p

Re: Not listing proxy_pass port 8009

2013-07-23 Thread Nikolas Stevenson-Molnar
"502 Bad Gateway" almost always means something is wrong with the upstream server (i.e., Nginx is working fine, whatever it's proxying to is having problems) so look for a problem there. _Nik On 7/23/2013 4:41 PM, imran_kh wrote: > Hello, > > Thanks for the reply, > > Actually openerp is also hos

Re: Not listing proxy_pass port 8009

2013-07-23 Thread imran_kh
Hello, Thanks for the reply, Actually openerp is also hosted on this server. Is this create “502 bad gateway” error? Please find the error log and suggest me on this. #openerp-error.log 2013/07/23 18:21:15 [error] 1465#0: *196 connect() failed (111: Connection refused) while connecting to upstre

Re: Not listing proxy_pass port 8009

2013-07-23 Thread Jonathan Matthews
On 23 July 2013 20:20, imran_kh wrote: > Thanks for the reply. I have never worked on Nginx server. So please help me > to resolve the issue. You've been told what the problem is 3 times already. It's nothing to do with nginx. The problem is that the process that nginx has been configured *to*tal

Re: Not listing proxy_pass port 8009

2013-07-23 Thread imran_kh
Hello, Thanks for the reply. I have never worked on Nginx server. So please help me to resolve the issue. File /etc/nginx/nginx.conf content are as follow. user www-data; worker_processes 4; pid /var/run/nginx.pid; events { worker_connections 768; # multi_accept on; } http {

Re: Not listing proxy_pass port 8009

2013-07-23 Thread Miguel C.
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

Re: Not listing proxy_pass port 8009

2013-07-23 Thread imran_kh
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 __

Re: Not listing proxy_pass port 8009

2013-07-23 Thread Richard Kearsley
the port in proxy_pass is not for listening/accepting incoming connections - it is for connecting outwards to another server/service You must have something else (another httpd, probably not nginx) listening on 8009..? On 23/07/13 17:39, imran_kh wrote: Hello, I am using Nginx web server

Re: Not listing proxy_pass port 8009

2013-07-23 Thread B.R.
Your configuration means that Nginx is listening on port 80 and will forward any request form example.com to a backend located on localhost listening on port 8009. Since Nginx is a proxy, you need a backend to serve content to which requests sent to Nginx will be forwarded. You seem not to unders

Not listing proxy_pass port 8009

2013-07-23 Thread imran_kh
Hello, I am using Nginx web server and getting error “502 bad gateway” while accessing some sites. I have observed that, proxy_pass port is not listing in the server. e.g.:- In above configuration example.com is running on port 80 and proxy_pass localhost is running on port 8009. Port 80 is listi