• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

URGENT: Plesk throwing PleskFatalException

G

GuillaumeS

Guest
Hi there,

Logged this morning to Plesk and it was asking me to confirm my password, ip etc once logged in... Just as it did when installed it for the first time... So I just filled the proper "Password confirmation" fields with the same value I used to loggin...
And now I have this error message:

ERROR: PleskFatalException
Dashboard preset used by user failed: DashboardPreset: unable to select: no such row in the table

Additionally, an exception has occurred while trying to report this error: PleskFatalException
Dashboard preset used by user failed: DashboardPreset: unable to select: no such row in the table

0: /opt/psa/admin/plib/user/UserAdmin.php:226
UserAdmin->getDashboardPreset()
1: /opt/psa/admin/plib/class.Form.php:237
Form->assign()
2: /opt/psa/admin/plib/class.AdminEditForm.php:142
AdminEditForm->assign(array, array, array)
3: /opt/psa/admin/htdocs/server/admin_ed.php3:263

What happened and how can I correct that ?
My clients accounts are working, only the admin can't access his prefs...

Thanks for any help !

Best regards.
 
Thought this might help to resolve my problem:

- I have this in my logwatch:

Unable to connect to Plesk Database: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2): 1 Time(s)

And below also in logwatch:

New Users:
plesk-root (10017)


Added User to group:
root:
plesk-root

Changed UID:
User plesk-root changed UID form 10017 to 0

- I have done several ssh commands the day before the problem appeared, to change my SQL password such as:
mysqladmin -p password my_new_password -u root!=??
mysql --user=root --pass=my_new_password

-With the help of:
/usr/bin/mysqld_safe --skip-grant-tables &

This should be obvious to someone !

Can't access further into Plesk than the fatal message displayed in the first post !

Rather embarrasing...
 
Hi GuillaumeS,

please check your system for rootkits. (http://www.chkrootkit.org)
I found this entry ("plesk-root") on one of my server too.
And this is realy bad!

And your "Master-User" for MySQL is not "root". It's "admin". (Don't know why Plesk do that... :( )

huschi.
 
Back
Top