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

Resolved Plesk Migration tool - Access to API is disabled for x.x.x.x

Thommato

New Pleskian
I've encountered an issue with the following module/plug-in within Plesk called 'Plesk Migrator'.

I cannot connect with the source server, I'm getting the following error: Failed to connect to target Plesk server by Plesk API: Plesk error [1006]: Access to API is disabled for x.x.x.x

I enabled the API within the configuration file (Panel.ini) of Plesk into the following:
[api]
allowedIPs = x.x.x.x

And this works, because the first time I got the following error:
{
"code": 0,
"message": "Access to API is disabled for x.x.x.x"
}
And now I get a login window that asks for the username and password.

So, this is enabled and must work. But it still gives me the error.

Now my question is, how to fix this, and how does the destination server know the API login and password, because it asks for it and you cannot specify those details within the tool?
 
Back
Top