mysql permissions bug
Posted: Wed May 10, 2017 7:31 pm
Hello,
I've just installed latest version of VesaCP at clear Debian8 server, all settings are default.
Then I added a web domain (+dns +mail), deleted default mysql database and created a new one for this website.
Using phpmyadmin I imported a sql dump, the site was OK. Then I installed LetsEncrypt SSL and edited some php scripts. This time the phpmyadmin session expired. When I logged in there again, I was not able to view any table contents due to
Some time ago I installed VestaCP at different VPS, there were problems with webmail. Everything ended when I installed clean webmail distribution into / of my own subdomain named mail and set that path in control panel config.
I've never experienced such problems with old VestaCP versions, everything MUST work from the box as it was before.
Of course I can fix it manually what I will do now, but why? There was a great benefit of VestaCP, when any user without an experience could install and use it, now it seems only experienced users may do it.
I've just installed latest version of VesaCP at clear Debian8 server, all settings are default.
Then I added a web domain (+dns +mail), deleted default mysql database and created a new one for this website.
Using phpmyadmin I imported a sql dump, the site was OK. Then I installed LetsEncrypt SSL and edited some php scripts. This time the phpmyadmin session expired. When I logged in there again, I was not able to view any table contents due to
error. Still I was able to view the table structure. Shit happens. I changed mysql user password using VestaCP, the same. There is a message about an controluser configuration errors in the page footer.#1142 - SELECT command denied to user 'admin_***'@'localhost' for table 'pma_table_uiprefs'
Some time ago I installed VestaCP at different VPS, there were problems with webmail. Everything ended when I installed clean webmail distribution into / of my own subdomain named mail and set that path in control panel config.
I've never experienced such problems with old VestaCP versions, everything MUST work from the box as it was before.
Of course I can fix it manually what I will do now, but why? There was a great benefit of VestaCP, when any user without an experience could install and use it, now it seems only experienced users may do it.