- Plesk Onyx for Linux
WordPress Toolkit fails to add a remote server/instance with the error:
PLESK_INFO: Connection refused
Random operations on a remote server/WordPress instances fail or hang with the errors:
PLESK_INFO: ssh: connect to host 203.0.113.2 port 22: Connection refused
PLESK_INFO: IP address not detected
PLESK_INFO: This WordPress installation might not be functioning properly or it's a copy of another installation.
Connections from the WordPress Toolkit server are blocked by intrusion detection algorithm or rate limit on the remote server side.
WordPress Toolkit connects to a remote server via SSH (port 22), HTTP (port 80) and HTTPS (port 443). There should be no limits for these connections coming from the WordPress Toolkit server.
White-list the WordPress Toolkit server IP address in Fail2ban and firewall:
If the remote server has Fail2ban
On the remote Plesk server, go to Tools & Settings > IP Address Banning (Fail2Ban).
Switch to the Trusted IP Addresses tab and click Add Trusted IP to add the IP address of a WordPress Toolkit server.
Connect to the remote server via SSH.
Open the file
/etc/fail2ban/jail.localin a text editor. In this example, we are using the vi editor:
# vi /etc/fail2ban/jail.local
Add the IP address of the WordpPress Toolkit server to the ignoreip parameter under the [DEFAULT] section:
ignoreip = 127.0.0.1/8 203.0.113.2 ...
Save the changes and close the file.
# service fail2ban reload
Refer to fail2ban documentation for more details.
If the remote server has a configured firewall
managed by iptables
managed by Uncomplicated Firewall (UFW)