• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Plesk 12.5 PSA-Firewall Custom Rules add unnecessary DROP rules.

paulieG

Regular Pleskian
Hi,
Testing Plesk 12.5 firewall.

If I create custom rule :


Test Allow incoming from XXX.XXX.XXX.XXX on all ports

Then the following iptables rules are generated :

/sbin/iptables -A INPUT -p udp -s XXX.XXX.XXX.XXX -j ACCEPT
/sbin/iptables -A INPUT -p udp -j DROP
/sbin/iptables -A INPUT -p tcp -s XXX.XXX.XXX.XXX -j ACCEPT
/sbin/iptables -A INPUT -p tcp -j DROP
/sbin/ip6tables -A INPUT -p udp -s ::ffff:XXX.XXX.XXX.XXX -j ACCEPT
/sbin/ip6tables -A INPUT -p udp -j DROP
/sbin/ip6tables -A INPUT -p tcp -s ::ffff:XXX.XXX.XXX.XXX -j ACCEPT
/sbin/ip6tables -A INPUT -p tcp -j DROP


This is is a bit of a problem is it not? When can we see a fix?

Paul.
 
I can't reproduce this issue on my default test Plesk 12.5 installation.
Could you please provide more detail? Step-by-step instruction for reproducing would be great.
 
Hi.

I have same issue.
When you add custom rules into the firewall, and if in rules present source ip - rules created wrong:
as example from "preview":
/sbin/iptables -A INPUT -p udp -s 40.40.40.40 -j ACCEPT
/sbin/iptables -A INPUT -p udp -j DROP
/sbin/iptables -A INPUT -p tcp -s 40.40.40.40 -j ACCEPT
/sbin/iptables -A INPUT -p tcp -j DROP
/sbin/ip6tables -A INPUT -p udp -s ::ffff:40.40.40.40 -j ACCEPT
/sbin/ip6tables -A INPUT -p udp -j DROP
/sbin/ip6tables -A INPUT -p tcp -s ::ffff:40.40.40.40 -j ACCEPT
/sbin/ip6tables -A INPUT -p tcp -j DROP

/sbin/iptables -A INPUT -p tcp --dport 100 -s 50.50.50.50 -j ACCEPT
/sbin/iptables -A INPUT -p tcp --dport 100 -j DROP
/sbin/ip6tables -A INPUT -p tcp --dport 100 -s ::ffff:50.50.50.50 -j ACCEPT
/sbin/ip6tables -A INPUT -p tcp --dport 100 -j DROP



I added 2 custom rules:
first: allow tcp 100 from 50.50.50.50
second: allow all from 40.40.40.40

If rules applied - all traffic will block.

Please help us to resolve this issue.
 
I have a similar related issue on a fresh install exactly the same set up (CentOS 6 Plesk 12.5). Upon adding a custom rule in Plesk firewall (opening passive FTP ports), all connections Pop and Imap via ports 995 and 993 are denied, and despite them being indicated as open using SSH root command openssl s_client -showcerts -connect mail.mydomain.tld:995
I tried adding a custom rule in /etc/sysconfig/iptables and restart but this just blocked all ports
It looks as if iptables (and ip6tables) are not actually started as a service??
 
Back
Top