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

Issue Plesk Migrator - Plesk error [11003]: PleskAPIInvalidSecretKeyException : Invalid secret key usage

Reese Jenner

New Pleskian
Hi.

My target is running Plesk Obsidian 18.0.30 Update #2 and the source (new Plesk install) is running 18.0.30 Update #2 as well.

When I try and do a migration on the source I get the following error:
Failed to connect to target Plesk server by Plesk API: Plesk error [11003]: PleskAPIInvalidSecretKeyException : Invalid secret key usage. Please check logs for details.

Searching the web came up with no solution.
I'm at a bit of a loss.
 
Do you have Source Plesk server behind NAT? In this case, it may be related to Plesk migrator bug #PMT-3846
As a workaround manually configure the migrated domain DNS zone as a slave and provide target server IP as a master DNS.
For additional information refer to the following article How to configure Plesk as a slave DNS server
 
Back
Top