• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

MySQL Admin Account vanished???

K

knocx

Guest
This morning i had found one of our servers PLESK login returning error like ;

Unable to connect to database: saved admin password is incorrect. 0: /usr/local/psa/admin/auto_prepend/auth.php3:66 psaerror(string "Unable to connect to database: saved admin password is incorrect.")

i had tried to reset the password but i realized that there were no users named admin.


we had audit the server and couldnt find any compromise signatures.

This is also interesting that if some one can found a way of priviledged access yo MySQL why on eath he would delete the user admin? Since after deletion he would not be able to access any mySQL relevant sources like PLESK , he could have logged in with this password...,

Since this is an interesting problem and i had read similar post on the forum i wanted to share my experiences with you

Any ideas comments are appreciated :)


-- knocx
 
Originally posted by knocx
This is also interesting that if some one can found a way of priviledged access yo MySQL why on eath he would delete the user admin? Since after deletion he would not be able to access any mySQL relevant sources like PLESK , he could have logged in with this password...
But if someone did already break in, if they wanted information, they probably already got it, then deleted the admin account to wreak havok on your server, and of course your hosted domains.
 
i dont know .... i noticed 4-5 posts similar to ours, they also dont report any attack signatures.
 
Back
Top