• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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