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 4 matches
- Fri Nov 19, 2021 8:17 pm
- Forum: General Discussion
- Topic: Compatibility with EL family
- Replies: 0
- Views: 4659
Compatibility with EL family
Hi there, We are a hosting company, we use cPanel mostly but every once in a while we support some community projects or are asked about low-budget solutions and for those we end setting up some free panel. We've used Vesta for a while on a customer, but there were some pesky bugs we've found we wer...
- Tue Sep 24, 2019 8:48 pm
- Forum: General Discussion
- Topic: Vesta packages infected
- Replies: 6
- Views: 11679
Re: Vesta packages infected
Thank you for all the answers.
A follow up question, if roundcube isn't used by VestaCP why is the package there? Or is there some option to enable roundcube? maybe there is lol.
Cheers guys
A follow up question, if roundcube isn't used by VestaCP why is the package there? Or is there some option to enable roundcube? maybe there is lol.
Cheers guys
- Tue Sep 24, 2019 8:17 pm
- Forum: General Discussion
- Topic: Vesta packages infected
- Replies: 6
- Views: 11679
Re: Vesta packages infected
I don't have roundcube installed on the server, never installed it nor was thinking of any by any manner.
The location of the infected file was `/usr/local/vesta/install/` hence finding it ... strange. Or was a hacked wordpress install that placed the file there?
The location of the infected file was `/usr/local/vesta/install/` hence finding it ... strange. Or was a hacked wordpress install that placed the file there?
- Tue Sep 24, 2019 7:44 pm
- Forum: General Discussion
- Topic: Vesta packages infected
- Replies: 6
- Views: 11679
Vesta packages infected
Dear Vesta Community, Recently I dabbled with a spreading infection on websites hosted at one server. After cleaning up the mess while doing a system-wide scan I found the following: [root@web ~]# clamscan -r --bell -i / --detect-pua=yes --exclude-dir=^/sys --exclude-dir=^/dev --exclude-dir=^/proc /...