• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Migration Giving Error, Saying IP address is not valid when it is

J.Wick

Regular Pleskian
Server operating system version
Centos 7.9
Plesk version and microupdate number
18.0.46 Update #1
Running dual servers with Plesk Version 18.0.46 Update #1 both on Linux.

I'm trying to run a migration and get the error:

' xxx.xx.xx.x' does not appear to be a valid IP address. This is the main public IP of the server and is pingable from the new server. Is this a bug?:eek:

If I try the Private IP, the "Preparing migration" starts up and fails with the error.

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

I've added public and private IPs of each server to the IP restriction allow lists of each server.

Ports open are 80,110,143,443,8443,8447 plus a non-standard SSH port.

I've enabled root login with SSH and restarted services, and verified connection via SSH using the key method.

I'm totally at a loss why something simple isn't working at all. Where are the API settings? I've added the API enabled and IP address permissions in the panel.ini of the source server and rebooted. I get nothing.
 
I ran Plesk repair all and then visited the Rest API sandbox, deleted all the API keys and made a new one for the new IP, removed all the IP restrictions on each server, and finally, it's connecting. This was NOT a smooth experience; migration needs to be refined and made child easy. Blew away 2 hours on this. :(

I'm still not sure what exactly fixed it definitively.
 
Back
Top