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

[Reese Jenner]

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.

 

[IgorG]

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

 

[vanlier]

Sorry to bump an old thread, but I'm at the beginning of migrating 250+ domains from an old CentOS plesk server to a new CloudLinux plesk server using Plesk migrator. The new server is behind NAT and when running I get the 'invalid secret key usage'. I can see in the debugging log that the secret key generation command uses the intern IP of the new server instead of the public ip.

Surely I'm not the first to have a plesk server behind NAT and this issue has been posted 4 years ago. Is there a fix/update/workaround available? Manually fixing DNS for al these domains isn't only time consuming but prevents bulk migration due to the extra downtime because of these manual actions.

 

[Sebahat.hadzhi]

Hello, @vanlier . Do I correctly understand that in your case only the destination server is behind NAT or is the source server as well? If it's the target server only, could you please try re-installing the Migrator extension on it?