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.
Email error connection database
Email error connection database
Hello ! :)
I have a server for my website I have done installed by a system administrator. She did not say to me that there had VestaCP backups on the database. For safety, I disabled the "root" user in the database. Since then, each morning I received the following mail :
From : Cron Daemon
Subject : Cron <admin@sd-91502> sudo /usr/local/vesta/bin/v-update-sys-queue disk
Message : Error: Connection to localhost failed
How to fix this? If possible, use a different user "root" ?
I thank you in advance ! :-)
I have a server for my website I have done installed by a system administrator. She did not say to me that there had VestaCP backups on the database. For safety, I disabled the "root" user in the database. Since then, each morning I received the following mail :
From : Cron Daemon
Subject : Cron <admin@sd-91502> sudo /usr/local/vesta/bin/v-update-sys-queue disk
Message : Error: Connection to localhost failed
How to fix this? If possible, use a different user "root" ?
I thank you in advance ! :-)
Re: Email error connection database
Changing the password for the user is not enough?yann74 wrote: I have a server for my website I have done installed by a system administrator. She did not say to me that there had VestaCP backups on the database. For safety, I disabled the "root" user in the database. Since then, each morning I received the following mail :
Re: Email error connection database
Thanks for your answer !
I had read somewhere that to improve safety, it was better to disable the user "root" and replace it with another user.
But if VestaCP can only function with the user "root" I would adapt :-)
I had read somewhere that to improve safety, it was better to disable the user "root" and replace it with another user.
But if VestaCP can only function with the user "root" I would adapt :-)