Welcome! Log In Create A New Profile

Advanced

Re: The service is not available. Please try again later.

w.b
March 15, 2013 08:12AM
> From: "Reddirt" <nginx-forum@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@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.

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

The service is not available. Please try again later.

Reddirt March 14, 2013 04:19PM

Re: The service is not available. Please try again later.

Reddirt March 14, 2013 04:31PM

Re: The service is not available. Please try again later.

Reddirt March 14, 2013 06:03PM

Re: The service is not available. Please try again later.

w.b March 15, 2013 08:12AM

Re: The service is not available. Please try again later.

Reddirt March 16, 2013 01:52PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 138
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready