• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

PSA Server Can't Start After Upgrade to 11.0.9

Ernie@

Basic Pleskian
Having upgraded to the latest version 11.0.9 from 11. The PSA server can't start and there's an HTTP 500 Internal Server Error when accessing the panel.

/var/log/sw-cp-server/error_log shows
-----------------------
2012-09-13 02:28:42: (mod_fastcgi.c.2746) FastCGI-stderr: PleskFatalException: Unable to obtain secret key for passwords encryption.
file: /usr/local/psa/admin/plib/Plesk/Base/Utils/String.php
line: 330
code: 0
trace: #0 /usr/local/psa/admin/plib/common_func.php3(3453): Plesk_Base_Utils_String::getCryptKey()
#1 /usr/local/psa/admin/auto_prepend/auth.php3(191): get_failure_redirect_url('failure_redirec...')
#2 {main}
--------------------------

Tried bootstrapper.sh repair, it says,
------------------------
Passwords for some MySQL users were not upgraded.
All MySQL DB users that may be used by Panel MUST have passwords in new 41-character format in order for Panel to function properly.
Currently following users have passwords in old format: billing@localhost, aspcomplete@%, aspcomplete@localhost, aspcsk@%, aspcsk@localhost, aspcss@%, aspcss@localhost, aspsession@%, aspsession@localhost.
Please ensure that MySQL server is not forced to use old password hashing algorithm and upgrade password format manually for users from the list above. Consult with MySQL server manual on detailed steps.
You may skip certain users if you are sure they weren't created and aren't used by Panel.
----------------------------

What should I do to fix the problem?

Regards,
 
bootstrapper repair, suggested to update the password format for the following accounts


Tried bootstrapper.sh repair, it says,
------------------------
***** problem report *****
Passwords for some MySQL users were not upgraded.
All MySQL DB users that may be used by Panel MUST have passwords in new 41-character format in order for Panel to function properly.
Currently following users have passwords in old format: billing@localhost, aspcomplete@%, aspcomplete@localhost, aspcsk@%, aspcsk@localhost, aspcss@%, aspcss@localhost, aspsession@%, aspsession@localhost.
Please ensure that MySQL server is not forced to use old password hashing algorithm and upgrade password format manually for users from the list above. Consult with MySQL server manual on detailed steps.
You may skip certain users if you are sure they weren't created and aren't used by Panel.
ERROR while trying to find MySQL ODBC driver
----------------------------

Any idea?

Thanks.
 
Last edited:
Since there's a need to update the password for the following accounts,

billing@localhost, aspcomplete@%, aspcomplete@localhost, aspcsk@%, aspcsk@localhost, aspcss@%, aspcss@localhost, aspsession@%, aspsession@localhost.

How can I get the password for those accounts?

Thanks
 
I've been hit by this "Unable to obtain secret key for passwords encryption" stuff-up this morning when upgrading one server from 10.4.4 to 11.0.9. The installer crashed halfway through leaving us with an unusable, almost upgraded plesk 11 instance. I've regenerated the key running "dd if=/dev/urandom of=secret_key bs=16 count=1" but still no joy. Then I've managed to fix this properly running:
yum --nogpgcheck reinstall plesk-core-11.0.9-cos5.build110120608.16.x86_64.rpm (why don't you sign your packages, Parallels?)
After logging into the Panel Plesk complained about the license being invalid, which I fixed clicking on "Retrieve keys".
 
Back
Top