Vesta Control Panel - Forum

Gmail distrusts by default the emails sent from unknown IPs and classifies them as spam. The fastest way to solve this is to ask Gmail users to send you a new email. From that moment, those users will receive your emails in their inbox. Over time, Gmail will trust your IP and distribute your email t...

You can add a new rule in "VestaCP/Firewall/Fail2Ban/+". For example, 123.123.123.0/24 blocks all IPs from 123.123.123.0 to 123.123.123.254 for ever.

You can create a new Fail2Ban filter in /etc/fail2ban/filter.d/ directory from a existing one, modify it and apply to a jail. Only one filter can be used in every jail, so could be necesary to add another.

You can do it from "VestaCP/Firewall/Fail2Ban list/+", but Fail1Ban would do automatically.

You can config Fail2Ban for RoundCube intrusions and config a long time ban in Fail2Ban for recurrent IP's too.

You can try "umask 022" for default permissions: https://www.cyberciti.biz/tips/understa ... usage.html

Try:

You must to add to "/etc/fail2ban/jail.local" file (in Server > Fail2Ban > Configure) the next jail: For Debian/Ubuntu: [roundcube-auth] enabled = true action = vesta[name=WEB] logpath = /var/log/roundcube/errors maxretry = 5 For CentOS: [roundcube-auth] enabled = true action = vesta[name=WEB] logpa...

Added to initial post: The only way I found to view banned IPs in VestaCP backend is to assigning "recidive" jail to a preexisting ban category and preferably unused (like DB or DNS), adding a new action line: [recidive] enabled = true action = vesta[name=DB] maxretry = 3 findtime = 86400 bantime = ...

Thanks for your time. I installed it on a Centos v7 VPS from root account through SSH. According to memory, everything related to the domains I did from the control panel and the admin account, even apply "sudo /usr/local/vesta/bin/v-update-host-certificate 'admin' $HOSTNAME". I have to say that eve...

In "VestaCP/Server/$HOSTNAME/Configure/Vesta SSL/Use Web Domain SSL Certificate" there is a domain and subdomains list like this: root:domain.tld root:mail.domain.tld But when I choose one and save the changes, I recive the error message: Error: user root doesn't exist. Somebody has this problem too...