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.
MySQL permissions problem? Can't access Vestacp
MySQL permissions problem? Can't access Vestacp
Hi, few days ago the server received an attack from China (DoS attack). I could stop it blocking ranges of IP addresses, setting a limit of login attempts, and everything seemed fine.
However since then I can't access the control panel (root or user), neither FTP, and the sites with MySQL databases show error 500.
When I try to recover the user password (via Vestacp login page), I can access but if I close the conection and try to access again, the panel says me that the password is wrong. This method does not work with the root user (main vestacp user).
By SSH the system tells me that the root user does not exist in vestacp.
The user 'admin' exists but I can`t login with it, and I have already changed the password by ssh. Anyway it is not the user that I used to manage the panel, I did it using root user.
Any idea, or help in this issue?
Thanks in advance
However since then I can't access the control panel (root or user), neither FTP, and the sites with MySQL databases show error 500.
When I try to recover the user password (via Vestacp login page), I can access but if I close the conection and try to access again, the panel says me that the password is wrong. This method does not work with the root user (main vestacp user).
By SSH the system tells me that the root user does not exist in vestacp.
The user 'admin' exists but I can`t login with it, and I have already changed the password by ssh. Anyway it is not the user that I used to manage the panel, I did it using root user.
Any idea, or help in this issue?
Thanks in advance
Re: MySQL permissions problem? Can't access Vestacp
Solved, was logs files inside tmp folder. The attack generates large log files. Deleted and all works fine.