• 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

Resolved Plesk 12 Firewall / CentOS 7

N_Vas

Basic Pleskian
I have the Plesk Firewall module installed.

When I enabled Rules Management it seems to been using IPTABLES (based on that script it shows you just before enabling the rules)

My question is, with CentOS7, centOS uses "firewalld" instead of "iptables"

A status of firewalld shows it is running:

--
# systemctl status firewalld
firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)
Active: active (running) since Sun 2015-05-10 06:35:13 EDT; 1 weeks 1 days ago
Main PID: 786 (firewalld)
CGroup: /system.slice/firewalld.service
ââ786 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid

May 10 06:35:13 www4 systemd[1]: Started firewalld - dynamic firewall daemon.
--


This is a new Plesk build and today we noticed we could not FTP into the server, so I went to the Plesk Firewall and enabled rule management. Then we could FTP in.


What firewall is Plesk managing (iptables or firewalld)?


Is it correct to be adding/modifying rules from within the Plesk Firewall when CentOS 7 is the operating system?


Thanks
 
The Plesk firewall is using iptables. Firewalld and iptables are not working well together - after a reboot it can happen
that all ports to the server are closed (I encountered this problem every time, had to reload firewalld to resolve it).
So you should stop and disable firewalld.

systemctl stop firewalld
systemctl disable firewalld

Btw - you should add a passive port range in the proftpd config and add
the correspondig rule to the plesk firewall.

Best regards
 
I couldn't connect ftp or plesk after a server reboot using centos 7 and plesk 12

Stopping firewalld solved my problem, I also disabled it.

Thank you very much
 
Back
Top