• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Plesk 10.4.4 does not store firewall rule

metalalisa

Basic Pleskian
After upgrade to 10.4.4 I try to add IP subnet x.x.0.0/8 to firewall rule and store it, but receive the error "Неверный IP-адрес или сеть". I even try to store rule without changes - the same error.

Please fix.
 
Hi, metalalisa.

Thanks you for feedback.

Could wou, please provide some details about your firewall issue: from which version of Plesk you made upgrade and on which operating system?
 
CentOS release 5.7 (Final)
Linux xxxx.xx 2.6.18-274.3.1.el5.centos.plus #1 SMP Wed Sep 7 05:38:58 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux

Upgrade was from Plesk 10.3.x
Code:
# iptables -V
iptables v1.3.5
 
After upgrade to 10.4.4 I try to add IP subnet x.x.0.0/8 to firewall rule and store it, but receive the error "Неверный IP-адрес или сеть". I even try to store rule without changes - the same error.

Please fix.

metalalisa, this is a known problem. Fix will be available in one of the next microupdates.
I will inform you when it will be available.
 
Last edited:
i think its too sensitive rules for ip(subnet).

i can't store

204.8.136.0/21,216.179.176.0/22, 202.43.104.0/22, 210.175.83.0/24, 211.147.208.0/20,202.171.224.0/21,211.100.0.0/18, 210.146.22.0/24
219.235.208.0/20, 218.246.0.0/19, 203.142.214.0/24, 208.101.0.0/18,
216.179.180.0/23, 202.12.244.0/22, 61.128.0.0/15,211.8.56.0/21, 203.79.60.0/26,
190.252.0.0/14, 187.32.0.0/11,202.6.8.0/21,

but i can store

115.85.160.0/19,
175.106.64.0/18, 180.222.32.0/19, 27.123.224.0/24, , 119.252.32.0/19, 110.165.0.0/19, 119.82.152.0/21, 113.130.0.0/18, 112.64.0.0/15, 203.196.19.32/27, 121.101.219.0/24, 116.89.240.0/20, 120.80.0.0/13, 27.40.0.0/14, 114.112.224.0/23, 114.200.0.0/21, 59.52.0.0/14, 112.88.0.0/13, 120.80.0.0/13, 58.20.0.0/16, 116.66.176.0/20, 124.109.108.0/22, 103.10.192.0/22, 14.192.96.0/19, 101.0.28.0/22, 10.175.35.0/24, 125.76.128.0/17, 175.45.168.0/21, 103.29.72.0/22, 31.192.104.0/21, 61.157.0.0/16, 116.197.152.0/21, 203.79.60.64/26, 203.79.60.128/25, 91.218.244.0/22, 141.105.64.0/21, 58.252.0.0/14, 49.156.160.0/19, 27.50.12.0/22, 86.107.172.0/22, 89.250.208.0/20

i don't know why
 
not yet .... i'm waiting too............

my server catch too many SPAM... i want to close the port from spam network.
 
I know about it is, of course, are already doing.
However, I'm going to manage with the Plesk Firewall will continue to set conditions so that very many.

The only hope in a hurry.

Because This problem is affected to set "Common Allow Zone Transfer ACL" and the other parts .

Would not want to use a standard feature?
 
Back
Top