Resolved URGENT: Help lost permission on Master account

[doekia]

Server operating system version

AlmaLinux 8.10

Plesk version and microupdate number

not a clue

Hi all

In my attempt to change the master password using the CLI I have totally lost permission from such account
I first faced a 500 error DB exception: Unable to find row by field login with value admin in smb_users table
I've tried plesk bin repair to no avail
I've then applied the procedure /usr/local/psa/bin/init_conf -u -name Admin
Now I can access plesk but my master account does not have ANY permission
I've tried to create à new admin account with plesk bin admin_alias create which succeed but have the same permission issue on the plesk

Please advise

 

[Sebahat.hadzhi]

Hey, @doekia. This sounds like a corrupted database. Please try applying the solution for recreating the missing tables provided by Igor here. If that doesn't work, the next best option will be to consider getting in touch with our support team. To sign-in to support and open a ticket go to:

https://support.plesk.com

If you got your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative to get support directly from Plesk:

https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk

 

[doekia]

Hey, @doekia. This sounds like a corrupted database. Please try applying the solution for recreating the missing tables provided by Igor here. If that doesn't work, the next best option will be to consider getting in touch with our support team. To sign-in to support and open a ticket go to:

https://support.plesk.com

If you got your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative to get support directly from Plesk:

https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk

Hi thanks for the suggestion.
I've fixed the problem with a different approach, I've restored the psa database, then created an alternate admin user from the console and corrupted the password of the initial Admin to ensure no one can login with such

Regards