- Plesk for Linux
Connecting to Plesk, mail server and/or websites hosted on a Plesk for Linux server from specific IP address (for example, 203.0.113.2) fails:
CONFIG_TEXT: This site can’t be reached
203.0.113.2 took too long to respond.
From other IP addresses, websites are accessed successfully.
Fail2Ban is installed and enabled.
203.0.113.2can be found in Plesk UI in Tools & Settings > IP Address Banning (Fail2Ban) > Banned IP Addresses or via CLI:
# plesk bin ip_ban --banned
Banned IP addresses:
203.0.113.2 plesk-panel Jan 1, 2018
- The following error may appear in Domains > example.com > Logs or in
CONFIG_TEXT: [:error] [pid 9833:tid 140526649054976] [client 203.0.113.2:49234] [client 203.0.113.2] ModSecurity: Access denied with code 403 (phase 2). Operator EQ matched 0 at REQUEST_COOKIES_NAMES. [file "/etc/apache2/modsecurity.d/rules/comodo_free/26_Apps_WordPress.conf"]
IP address 203.0.113.2 is banned by Fail2Ban.
Note: In commands below
203.0.113.2 is an IP-Address from where it is not possible to access Plesk and sites.
Unban the IP-address or add it to trusted IP-addresses
203.0.113.2 to Fail2ban white list:
- Go to Tools & Settings > IP Address Banning (Fail2Ban) > Banned IP Addresses
Select the IP address
203.0.113.2either click Unban or click Move to Trusted IPs
- Connect to the server via SSH.
Unban the IP-Address:
# plesk bin ip_ban --unban 203.0.113.2
SUCCESS: The selected IP addresses were unbanned.
Add the IP-Address to the list of Trusted IP-Addresses
# plesk bin ip_ban --add-trusted 203.0.113.2
If ModSecurity blocked the IP, it may be required to disable the ModSecurity rule for a domain completely according to this article.