• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 Migrator: Failed to connect

Paul Hermans

Basic Pleskian
When trying to use the Plesk Migrator I get this error:

ERROR: "Failed to connect to target Plesk server by Plesk API: Plesk error [1006]: Access to API is disabled for 1.2.3.4"

Destination server:
Centos 8.1 + Plesk Obisidian Version 18.0.25 Update #2
Source servers tested: Centos 6.x + Plesk Onyx, Centos 7.x + Plesk Obisidian

Steps to reproduce:
1) Plesk > Tools & Settings > Migration & Transfer Manager
2) Start a New Migration
3) SSH + pw

What did I already check?

SSH access is confirmed using
# ssh 1.2.3.4

Plesk API is functioning normal, tested with other app

Panel.ini api settings are ok
I tested with allowedIPs=1.2.3.4
And without ip restrictions (allowedIPs commented out)

When watching /var/log/secure on the source server while connecting:
I see no log lines, so Plesk does not even try to connect to SSH.

It doesn't matter if I supply the correct or incorrect SSH password, same error message.

I am out of options.
Anybody any ideas?
 
Last edited:
OK, found it!

You need to put the IP-address of the destination server on the allowedIPs list of the API inside panel.ini on the destination sever itself.

(Apparently the Plesk migrator connects to itself using the Plesk API)
 
OK, found it!

You need to put the IP-address of the destination server on the allowedIPs list of the API inside panel.ini on the destination sever itself.

(Apparently the Plesk migrator connects to itself using the Plesk API)
Thanks for sharing this workaround. I was struggling with "Plesk error [1006]: Access to API is disabled" for a while and after reading your comment found a way to fix it.
 
Back
Top