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

Migration Error - 7.5 reloaded to brand new 8.3 install

B

bsoper

Guest
When I try to migrate, as soon as I put in my username/passwords and hit "go" I get a ton of errors and it just gives me a "migration failed". I am moving about 43 domains from one virtual server (using Parallels virtual servers of course) to another.

Any help on this? Thanks!



File "/usr/local/psa/admin/share/supervisor/processor.py", =
line 84, in getStatus
return (None, self.realGetStatus())
File "/usr/local/psa/admin/share/supervisor/processor.py", =
line 255, in realGetStatus
+ "/scout-result.xml").childNodes[0])
File "/usr/lib/python2.5/xml/dom/minidom.py", line 1913, in =
parse
return expatbuilder.parse(file)
File "/usr/lib/python2.5/xml/dom/expatbuilder.py", line 924, =
in parse
result =3D builder.parseFile(fp)
File "/usr/lib/python2.5/xml/dom/expatbuilder.py", line 211, =
in parseFile
parser.Parse("", True)
ExpatError: no element found: line 1, column 0
 
Hi
It is not possible to say anything for sure from the description you provided. Check the log files (usually located at /usr/local/psa/PMM/logs/) for more errors
 
Back
Top