• 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.

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