• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Error 10.2.0 > 10.2.0

GhOsTisp

Basic Pleskian
With errors when finished migration


<?xml version="1.0"?>
<execution-result status="error"><message code="InternalDtdValidationFailed" severity="error" id="447ea23d-1b1b-452f-8ecf-656ecaeaa70e"><description>Failed validation of the document with its internal DTD. The errors are: Element 'cid-rsync', attribute 'type': [facet 'enumeration'] The value 'sb5-site' is not an element of the set {'skeleton', 'docroot', 'docroot_ssl', 'cgi', 'error_docs', 'private', 'conf', 'admin_private', 'logs', 'anon_ftpstat', 'webuser_home', 'webuser_private', 'ftp_pub', 'ftp_incoming', 'mailbox', 'mailbox_inbox', 'mailmsg', 'mailnative', 'attaches', 'locale', 'skin', 'key', 'webstat', 'webstat_ssl', 'ftp_stat', 'statistics', 'spam-assasin', 'sapp-distrib', 'web-app', 'sapp-scripts', 'sapp-https-scripts', 'sapp-cgi-bin', 'sapp-htdocs', 'icon', 'vhost', 'domainmail', 'domainmaillist', 'vdirs', 'error_docs_cfg', 'sb-reseller', 'sb-domain', 'whole', 'aspnet_config', 'aps-cache', 'file-sharing', 'file-sharing-passwd', 'mailbox_whole', 'custom-apache-templates', 'branding-theme'}.Element 'cid-rsync', attribute 'type': 'sb5-site' is not a valid value of the local atomic type..</description></message></execution-result>
 
As possible workaround for error "Element 'cid-rsync', attribute 'type': 'sb5-site' is not a valid value of the local atomic type" you may choose option "Use configuration from current system and data from migration data file" in section "Timing Conflicts" of migration page "Resolution Rules For Migration Conflicts". It's "Use configuration and data from migration data file" set by default.
 
Back
Top