• 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.

Plesk error PleskAPIInvalidSecretKeyException : key is not found

jojoo

New Pleskian
TITLE:
Plesk error PleskAPIInvalidSecretKeyException : key is not found​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk obsidian 18.0.20​
PROBLEM DESCRIPTION:
I tried to run plesk migrator and I get the following error after updating my database to Mariadb 10.3.18

Failed to connect to target Plesk server by Plesk API: Plesk error [11003]: PleskAPIInvalidSecretKeyException : key is not found


My idea was to update the Plesk database to mirror the database version of cpanel in order to import accounts from Cpanel installation.​
STEPS TO REPRODUCE:
Install plesk obsidian
Install Plesk migrator
Update from Mariadb 5.5 to 10.3.18
Uninstall plesk migrator
Reinstall plesk migrator​
ACTUAL RESULT:
Failed to connect to target Plesk server by Plesk API: Plesk error [11003]: PleskAPIInvalidSecretKeyException : key is not found ​
EXPECTED RESULT:
No error​
ANY ADDITIONAL INFORMATION:
​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Help with sorting out​
 
[root@ns3 ~]# /usr/local/psa/bin/secret_key --list
Warning: Current locale is unusable. Using 'C' instead.
Key: ?qA?4?TAѮ}????^E?????ϰN?@?Jt>?qL????(k-
Ip: 5.79.119.68
Description: For Plesk Migrator extension

Key: c8e02af1-867c-f26b-a68a-7c84f27106fb
Ip: 5.79.119.68
Description:
 
Have you tried to set up English locale with

# export LC_ALL="en_US.UTF-8"

and repeat migration?
 
Back
Top