Report this

What is the reason for this report?

Nginx Error 111: Connection refused

Posted on June 8, 2016

I recently switched from Apache2 to Nginx for my web server because Apache was giving me some very weird issues that no one could seem to solve. I used this guide here to make the switch. Now, I see in my Nginx error log (located /var/log/nginx/error.log)

2016/06/07 18:41:50 [error] 3221#0: *53 connect() failed (111: Connection refused) while connecting to upstream, client: xxx.xxx.xxx.xxx, server: websitename.net, request: "POST /xmlrpc.php HTTP/1.0", upstream: "fastcgi://127.0.0.1:9000", host: "xxx.xxx.xxx.xxx"

The site was working fine up until a few days ago. I did not change any settings during that time. Here is my full Nginx config.



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

This comment has been deleted

Hi,

Im getting a similar error, but I have:

    # With php7.0-cgi alone:
    #       fastcgi_pass 127.0.0.1:9000;
    #       # With php7.0-fpm:
    #       fastcgi_pass unix:/run/php/php7.0-fpm.sock;

do I need to change unix:/run/php/php7.0-fpm.sock to 127.0.0.1:9000?

Also, /etc/php7/fpm/pool.d/www.conf is not found

Mine issue was slightly different I was reverse-proxying my subdomain wordpress blog site on my main site, and I wasn’t using PHP-fpm for handling PHP pages. the error was:
connect() failed (111: Connection refused) while connecting to upstream, client: xxx.xxx.xxx.xxx, server: “my.site.com”, request: GET /blog HTTP/1.0", upstream: “my.blog.site”, host: “my.site.com

the issue was in my blog server’s firewall where WordPress was blocking my site IP address.

check status of firewall #ufw status verbose if status active next

check the iptable #iptables -S check if list contains “f2b-wordpress-hard -s xx.main.site.ip.xx/32 -j REJECT --reject-with icmp-port-unreachable”

do #fail2ban-client set wordpress-hard unbanip xx.main.site.ip.xx

for more details visit: https://gist.github.com/stephenscaff/a0527da89b69dab57f93c09b4287b174

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.