• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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.

Issue Subscription migration via XML RPC API

sraman

New Pleskian
Server operating system version
CloudLinux 8.6
Plesk version and microupdate number
Obsidian 18.0.44
Hi,

Iam trying to use the XML RPC api to automate the subscription migration. And i created the request packet as follows. But i get an error response with code 1014 and the error text as "Parser error: Request is invalid. Error in line 2: Element 'migration': This element is not expected. Expected is one of ( request-settings, server, customer, webspace, subdomain, dns, db_server, mail, certificate, site-alias".

sample request:

<?xml version="1.0" encoding="UTF-8"?> <packet> <migration> <start> <host>xx.xxx.xx.xx</host> <login>xxxxxxx</login> <password>xxxxx</password> <destination-host-directory>/tmp</destination-host-directory> <content-transport>rsync</content-transport> <only-hosting/> <selected-objects> <migrate-webspaces> <target-owner>xxxxxxx</target-owner> <webspace> <name>somedomain.com</name> <ip> <new> <ip-type>shared</ip-type> <ip-address>ipv4Address</ip-address> <ip-address>ipv6Address</ip-address> </new> </ip> </webspace> </migrate-webspaces> </selected-objects> </start> </migration> </packet>

The request packet is formed as per the documentation. Is there something that i missing? Any help much appreciated.

Thanks!
 
Thanks for the quick respons. Is there any plan to have the migration operator via the XMP api in the near future in the current schema ? We have a need to automate the migration via the api.
Thanks for the quick respons. Is there any plan to have the migration operator via the XMP api in the near future in the current schema ? We have a need to automate the migration via the api.
Or is there any other schema that we can use to achieve the migration via api ? And we can still see documentation has the migration operator.

 
[...] And we can still see documentation has the migration operator.

Thats correct, however the documentation you're referring to is for the legacy Plesk 12.5 version. As the operator is no longer part of the XML API in newer Plesk versions, you won't find the operator mentioned in the documentation of those newer Plesk versions.

If you're looking for an alternative have a look a the migration options for the CLI.
 
Back
Top