• 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 stopped working API issue

Alaa Mansour

Basic Pleskian
Hello,

I was doing the migration, then suddenly I receive this:

Failed to connect to target Plesk server by Plesk API: Plesk error [1006]: Access to API is disabled for xx.xx.xx.xx

I have added the IP through plesk db:
mysql> insert into cp_access (type, netaddr, netmask) values ('deny' , 'xx.xx.xx.xx', '255.255.255.255');

I have added it also to fail2ban trusted IPs

I have added it also to Panel.ini under [api]
[api]
enabled = on
allowedIPs = xx.xx.xx.xx

what else?

PS: today I have configured ssl ciphers and TLS, but I issue plesk repair installation
 
I have managed to resolve the issue by putting the IP of the both servers inside [api] in both Panel.ini
and both server's IP inside IP Access Restriction Management.
I don't know why do I need to place the IP of itself. but now its working
 
Back
Top