- Plesk for Linux
There are several public IP addresses set up on a network interface (one on a primary interface, others on secondary interfaces).
All IP addresses are successfully read by Plesk and can be found at Tools & Settings > IP Addresses .
Randomly, Plesk and websites become inaccessible on one of the IP addresses with the
ERR_CONNECTION_REFUSEDerror. On others IP addresses, they work without any issues.
The affected IP address is not responding to ping requests from the external network:
# ping 203.0.113.2
PING 203.0.113.2 (203.0.113.2) 56(84) bytes of data.
--- 203.0.113.2 ping statistics ---
50 packets transmitted, 0 received, 100% packet loss, time 18575ms
Other IP addresses can be successfully pinged from the external networks.
From the server itself, the external networks can not be reached from this IP address, even the IP address of a gateway can not be reached also:
# ping -I 203.0.113.2 188.8.131.52
PING 184.108.40.206 (220.127.116.11) from 203.0.113.2 : 56(84) bytes of data.
--- 18.104.22.168 ping statistics ---
50 packets transmitted, 0 received, 100% packet loss, time 34271ms
# ping -I 203.0.113.2 203.0.113.1
PING 203.0.113.1 (203.0.113.1) from 203.0.113.2 : 56(84) bytes of data.
--- 203.0.113.1 ping statistics ---
50 packets transmitted, 0 received, 100% packet loss, time 85756ms
From others IP addresses, the above hosts can be pinged successfully.
Network misconfiguration which causes this intermittent network issue.
Contact network administrator to resolve the issue.