All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
MyVestaCP - fail2Ban and iptables
I have a few questions related to Fail2Ban and IPtables:
- In MyVestaCP, why uptime for iptables is always 0? Vestacp and Hestia have the same issue. All 3 show uptime =0 minutes for iptables.
- In jail.conf, enabled = false. So, it means all jails are disabled by default. True?
- jail.local has the following. It means only these jails are active. True?
- If I want to enable jail for apache or nginx, I will add them to the jail.local file. True?
[ssh-iptables]
enabled = true
filter = sshd
action = vesta[name=SSH]
logpath = /var/log/auth.log
maxretry = 5
[vsftpd-iptables]
enabled = false
filter = vsftpd
action = vesta[name=FTP]
logpath = /var/log/vsftpd.log
maxretry = 5
[exim-iptables]
enabled = true
filter = exim
action = vesta[name=MAIL]
logpath = /var/log/exim4/mainlog
[dovecot-iptables]
enabled = true
filter = dovecot
action = vesta[name=MAIL]
logpath = /var/log/dovecot.log
[mysqld-iptables]
enabled = false
filter = mysqld-auth
action = vesta[name=DB]
logpath = /var/log/mysql.log
maxretry = 5
[vesta-iptables]
enabled = true
filter = vesta
action = vesta[name=VESTA]
logpath = /var/log/vesta/auth.log
maxretry = 5
Comments
Thank you so much.
As @Lupu already said, it's because it's not a service... it's actually iptables rules