We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Search found 21 matches
- Sat Sep 28, 2019 9:38 am
- Forum: CLI
- Topic: CLI for beginners: v-search-command
- Replies: 2
- Views: 14026
Re: CLI for beginners: v-search-command
Thanks for to share.
- Mon Sep 02, 2019 9:15 am
- Forum: Mail Server
- Topic: Exim + Dovecot | Can't send email to gmail only
- Replies: 6
- Views: 6016
Re: Exim + Dovecot | Can't send email to gmail only
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...
- Fri Aug 16, 2019 3:18 pm
- Forum: General Discussion
- Topic: How to block permanent IP range on Fail2ban?
- Replies: 2
- Views: 3270
Re: How to block permanent IP range on Fail2ban?
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.
- Thu Jul 25, 2019 5:19 pm
- Forum: Mail Server
- Topic: How block IP in exim4
- Replies: 3
- Views: 3525
Re: How block IP in exim4
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.
- Mon Jul 22, 2019 3:01 pm
- Forum: Mail Server
- Topic: How block IP in exim4
- Replies: 3
- Views: 3525
Re: How block IP in exim4
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 config Fail2Ban for RoundCube intrusions and config a long time ban in Fail2Ban for recurrent IP's too.
- Sat Jul 06, 2019 8:17 am
- Forum: RHEL/CentOS
- Topic: How to default permissions for files / folders 644/755
- Replies: 6
- Views: 8412
Re: How to default permissions for files / folders 644/755
You can try "umask 022" for default permissions: https://www.cyberciti.biz/tips/understa ... usage.html
- Sat Jul 06, 2019 8:02 am
- Forum: RHEL/CentOS
- Topic: Cannot change server hostname
- Replies: 2
- Views: 2656
Re: Cannot change server hostname
Try:
Code: Select all
sudo hostnamectl set-hostname host.domain.tld
- Thu Jul 04, 2019 9:27 am
- Forum: Modification & Patches
- Topic: How to config Fail2Ban for RoundCube intrusions
- Replies: 0
- Views: 14329
How to config Fail2Ban for RoundCube intrusions
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...
- Thu Jul 04, 2019 8:50 am
- Forum: Modification & Patches
- Topic: How to config a long time ban in Fail2Ban for recurrent IP's
- Replies: 2
- Views: 17007
Re: How to config a long time ban in Fail2Ban for recurrent IP's
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 = ...
- Wed Jul 03, 2019 7:24 pm
- Forum: General Discussion
- Topic: Is there something wrong in my VestaCP instalation?
- Replies: 2
- Views: 2496
Re: Is there something wrong in my VestaCP instalation?
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...