• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

pleskrestore subdomain issue

J

jalder

Guest
Hello,

I am restoring a Plesk dump from Plesk 8.2 to a Plesk 8.6 box, it is a server level restore, the limits do not seem to be transferring correctly, this is causing the Plesk restore to fail on subdomains, as well as Mysql, and a few other things I have missed.

The errors logged thus far are:
<message code="NotAProperSubdomain" severity="error"><context>static std::string pl
esk::DnsRecordDeployer::getSubDomain(std::string, std::string)</context><file>./pmm_deploy.cpp</file><line>315
2</line><text> is not a proper subdomain of whateverdomain.com

Is there a particular reason the limits would fail to transfer and subsequently cause all of the data associated with those limits to fail?

Kind Regards,
John
 
Hi.

Quite hard to suggest anything at this point. Not even sure it is a limits issue. Can you post full log file here?

I would recommend contacting Parallels support team to get assistance with this or you can migrate data using Plesk migration manager instead of making backup/restore.
 
Back
Top