• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

XF 1.2 nginx xenforo error connect() failed (111: Connection refused) while connecting to upstream, client

Brent W

Well-known member
#1
I see this pop up frequently in my nginx error log. Different urls each time.

Code:
2013/11/19 20:40:45 [error] 12221#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 66.249.64.2, server: www.v6mustang.com, request: "POST /deferred.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "www.v6mustang.com", referrer: "http://www.v6mustang.com/members/avonmustang.15123/post-areas"
 

Brent W

Well-known member
#2
No ideas? This can't be normal...

here is a different one that just came in

Code:
2013/11/20 08:54:42 [error] 15593#0: *143 connect() failed (111: Connection refused) while connecting to upstream, client: 66.249.64.3, server: www.v6mustang.com, request: "GET /threads/updated-pics-of-my-car-cervinis-ram-air-hood-and-side-scoops.198747/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "www.v6mustang.com"
 

Mike

XenForo developer
Staff member
#3
That looks like an error coming from your FastCGI server. Perhaps it doesn't have any slots available to process the request?
 

Brent W

Well-known member
#4
Thanks. Being a newbie to nginx I am not sure about optimizations and such. I will poke around with that bit of information.
 

Tracy Perry

Well-known member
#5
Thanks. Being a newbie to nginx I am not sure about optimizations and such. I will poke around with that bit of information.
Quick Google search seems to confirm that it's your FCGI processor
This is not really an Nginx error. The problem is that the backend is not listening on port 9000 or its queue is filled up. I was unable to telnet to 127.0.0.1 9000. Restarting spawn-fcgi fixed this.
from here.

Best bet is that the queue is full.