The service is not available. Please try again later.
WBrown at e1b.org
WBrown at e1b.org
Fri Mar 15 12:11:41 UTC 2013
> From: "Reddirt" <nginx-forum at nginx.us>
> I got past that error and now the nginx error log has this:
>
> 2013/03/14 14:22:10 [error] 1537#0: *1 connect() failed (111: Connection
> refused) while connecting to upstream, client: 192.168.20.3, server: ,
> request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3000/", host:
> "ndeavor.ameipro.com"
> 2013/03/14 14:22:10 [error] 1537#0: *1 connect() failed (111: Connection
> refused) while connecting to upstream, client: 192.168.20.3, server: ,
> request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3001/", host:
> "ndeavor.ameipro.com"
> 2013/03/14 14:22:10 [error] 1537#0: *1 connect() failed (111: Connection
> refused) while connecting to upstream, client: 192.168.20.3, server: ,
> request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3002/", host:
> "ndeavor.ameipro.com"
> 2013/03/14 14:22:10 [error] 1537#0: *1 connect() failed (111: Connection
> refused) while connecting to upstream, client: 192.168.20.3, server: ,
> request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3003/", host:
> "ndeavor.ameipro.com"
> 2013/03/14 14:22:10 [error] 1537#0: *1 connect() failed (111: Connection
> refused) while connecting to upstream, client: 192.168.20.3, server: ,
> request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3004/", host:
> "ndeavor.ameipro.com"
> 2013/03/14 14:22:27 [error] 1537#0: *1 connect() failed (111: Connection
> refused) while connecting to upstream, client: 192.168.20.3, server: ,
> request: "GET /clients HTTP/1.1", upstream: "
http://127.0.0.1:3004/clients",
> host: "ndeavor.ameipro.com"
> 2013/03/14 14:22:27 [error] 1537#0: *1 connect() failed (111: Connection
> refused) while connecting to upstream, client: 192.168.20.3, server: ,
> request: "GET /clients HTTP/1.1", upstream: "
http://127.0.0.1:3000/clients",
> host: "ndeavor.ameipro.com"
> 2013/03/14 14:22:27 [error] 1537#0: *1 connect() failed (111: Connection
> refused) while connecting to upstream, client: 192.168.20.3, server: ,
> request: "GET /clients HTTP/1.1", upstream: "
http://127.0.0.1:3001/clients",
> host: "ndeavor.ameipro.com"
> 2013/03/14 14:22:27 [error] 1537#0: *1 connect() failed (111: Connection
> refused) while connecting to upstream, client: 192.168.20.3, server: ,
> request: "GET /clients HTTP/1.1", upstream: "
http://127.0.0.1:3002/clients",
> host: "ndeavor.ameipro.com"
> 2013/03/14 14:22:27 [error] 1537#0: *1 connect() failed (111: Connection
> refused) while connecting to upstream, client: 192.168.20.3, server: ,
> request: "GET /clients HTTP/1.1", upstream: "
http://127.0.0.1:3003/clients",
> host: "ndeavor.ameipro.com"
> 2013/03/14 14:22:28 [error] 1537#0: *12 no live upstreams while
connecting
> to upstream, client: 192.168.20.3, server: , request: "GET / HTTP/1.1",
> upstream: "http://backend/", host: "ndeavor.ameipro.com"
> 2013/03/14 14:23:09 [info] 1537#0: *1 client 192.168.20.3 closed
keepalive
> connection
> 2013/03/14 14:23:09 [info] 1537#0: *15 client 192.168.20.3 closed
keepalive
> connection
>
> Posted at Nginx Forum: http://forum.nginx.org/read.php?2,237379,
> 237382#msg-237382
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
Is the application listening on those ports? What does netstat show? Can
you telnet to the app server on those ports? Could the app not be
listening on 127.0.0.1 and only on the non-loopback address?
Confidentiality Notice:
This electronic message and any attachments may contain confidential or
privileged information, and is intended only for the individual or entity
identified above as the addressee. If you are not the addressee (or the
employee or agent responsible to deliver it to the addressee), or if this
message has been addressed to you in error, you are hereby notified that
you may not copy, forward, disclose or use any part of this message or any
attachments. Please notify the sender immediately by return e-mail or
telephone and delete this message from your system.
More information about the nginx
mailing list