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 31 matches
- Fri Oct 12, 2018 10:00 am
- Forum: General Discussion
- Topic: All VestaCP installations being attacked
- Replies: 230
- Views: 725393
Re: All VestaCP installations being attacked
flanders, Thank you for the information eduzro , when your server was installed ? I installed Vesta at the beginning of August. The panel already included the fix for the previous vulnerability. This time, after being hacked, I blocked the requests to the Vesta port and disabled the Vesta service u...
- Thu Oct 11, 2018 12:15 pm
- Forum: General Discussion
- Topic: All VestaCP installations being attacked
- Replies: 230
- Views: 725393
Re: All VestaCP installations being attacked
My server was hacked in september. The Vesta service was running and I had SSH access enabled just for the admin user. I set the password with the installation command. I don't know if the file /usr/bin/dhcprenew was in the server.
- Wed Sep 26, 2018 11:35 am
- Forum: General Discussion
- Topic: All VestaCP installations being attacked
- Replies: 230
- Views: 725393
Re: All VestaCP installations being attacked
Not even sure it's related to Vesta. For example, serious issue in kernel, published yesterday - https://access.redhat.com/security/cve/cve-2018-14634 I don't think it's because of this issue, as it first needs the access data of an unprivileged user (One of my servers which was hacked had only the...
- Wed Sep 26, 2018 10:46 am
- Forum: General Discussion
- Topic: All VestaCP installations being attacked
- Replies: 230
- Views: 725393
Re: All VestaCP installations being attacked
Do you think that disabling vesta service + disabling the access to the default vesta port can prevent the hacking?
- Tue Jan 31, 2017 5:16 pm
- Forum: DNS Server
- Topic: Possible bugs found in DNS KDIM string limit and MX records
- Replies: 5
- Views: 7198
Re: Possible bugs found in DNS KDIM string limit and MX records
Ok, thanks. Didn't know that existed : )
- Tue Jan 31, 2017 12:06 am
- Forum: DNS Server
- Topic: Possible bugs found in DNS KDIM string limit and MX records
- Replies: 5
- Views: 7198
Possible bugs found in DNS KDIM string limit and MX records
Hi; I spent this afternoon trying to create a DKIm key in order to use it with gsuite. If the string is too long it needs to be saparated with quotes. it can't be done throught the panel and, if entered, the dns zone for that domain won't load unless the conf/dns/domain.db file is edited manually. T...
- Wed Jan 25, 2017 3:03 am
- Forum: DNS Server
- Topic: DNS records do not display
- Replies: 1
- Views: 4584
Re: DNS records do not display
Solved after restoring a copy where some records were not added yet. It may happen a problem when double quotes (") and spaces are added to MX records.
- Wed Jan 25, 2017 1:56 am
- Forum: DNS Server
- Topic: DNS records do not display
- Replies: 1
- Views: 4584
DNS records do not display
Hi; A client of mine added some DNS records using the panel and for unknown reasons, are hidden. The records are working and I can even add more. It even says "/21" in the domain list, that is the number of records. But when i click to view and edit the records, the list is empty and it says "0 reco...
- Tue Jan 24, 2017 4:34 am
- Forum: Mail Server
- Topic: TLS & Certificate problem
- Replies: 2
- Views: 4820
TLS & Certificate problem
Hi; I have vestaCP in CentOS 6.7 and I'm trying to set a SSL certificate to exim and dovecot. I use default ports: 143 for IMAP and 587 for SMTP. However, when trying to connect, a message appears saying that the config is valid but the certificate have no data and that it's expired (it appears the ...
- Thu Jan 05, 2017 12:49 am
- Forum: Web Server
- Topic: JQuery Issues
- Replies: 2
- Views: 3285
Re: JQuery Issues
I Don't understand. jQuery has nothing to do with the server. Do you mean when you include the jQuery script or when you make ajax calls (for example using jQuery.post() ) ?