• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved connect() failed (111: Connection refused) while connecting to upstream

user3498724

New Pleskian
Hello, I am using Plesk Onyx 17.8.11 on Debian 9.4, and have a (Hetzner CX20) virtual server with private ip address 172.31.1.100 configured 1:1 via NAT on public IP 88.99.186.220.

When trying to open my website www.1luxuryphones.com I am getting ‘502 bad gateway nginx error’, and can see the following errors in /var/www/vhosts/system/1luxuryphones.com/logs/proxy_error_log:

*2018/04/08 15:20:43 [error] 4568#0: 2721 connect() failed (111: Connection refused) while connecting to upstream, client: 77.98.74.207, server: 1luxuryphones.com, request: "GET / HTTP/1.1", upstream: "http://172.31.1.100:7080/", host: "www.1luxuryphones.com", referrer: "http://www.1luxuryphones.com/"

In Plesk panel > Tools & Settings > IP addresses I have configured IP 172.31.1.100 so it has external IP 88.99.186.220.
However based on the proxy_error_log above it seems there is nothing listening on 172.31.1.100:7080, so the nginx cannot successfully forward the traffic.

Would someone know if more configuration should be done in Plesk to fix this issue?

Many thanks
 
Please check your network-config:

/etc/sysconfig/network-scripts/

Check this and please make sure that the settings for the IP are as they should be.

You can be sure to put the PHP interpreter from FPM(Nginx) to FastCGI(Apache).
 
i have the same problem and apache is runniong plesk website is working also just domains give 502 bad gateway ?
 
Back
Top