• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Migrate from Confixx 3.3 to Plesk 9.3

W

WolfgangM

Guest
Hi,

is there an easy way to migrate users from a confixx-Server to a plesk-Server? Or is there a best practise?
I have more than 70 Customers with more than 600 Domains on the Confixx and any help would be great.

Is there a possibility to copy at least the Mailboxes and Email-Addresses?

Here are some Problems where I hope I can get some help:
- The main thing: copy the mailboxes
- The websites have different locations which is a big problem in some Scripts.
- Database-Names are different
- there are some Websites where domainname.tld isn´t the same location than www.domainname.tld which was very easy in confixx
- I would like to copy User and Passwords from panel-Users, ftp-users and email-Accounts, so that users do not have to do a lot while the migration

Thanks for any suggestions
 
Confixx migration agent is attached.

How to install PMM:
http://download1.parallels.com/Plesk/PPP9/Doc/en-US/plesk-9.2-migration-guide/63301.htm

Plesk 9 PMM has no Confixx migration agent - it must be installed manually.

How to install Confixx migration agent:
1. Back up existed '/usr/local/psa/PMM/agents/shared' dir.
2. Remove existed '/usr/local/psa/PMM/agents/shared' dir.
3. Extract attached Confixx_Plesk9_agent.tar.gz to /usr/local/psa/PMM/agents.

How to migrate:
http://download1.parallels.com/Plesk/PPP9/Doc/en-US/plesk-9.2-migration-guide/63302.htm
 

Attachments

  • Confixx_Plesk9_agent.tar.gz
    193.1 KB · Views: 57
Last edited:
PMM does not work

Hi,

PMM creates Resellers and Users. But there is no content after the Migration. When I look in the tmp-Folder there are the transfered tar-Files. But I get this message while the Migration:

- <object name="mydomain.tld" type="hosting">
- <message code="CantUnpackDomainContent" severity="error">
<context>virtual void plesk::DomainVHostRefferred::Extract(plesk::ContentUnpacker&)</context>
<file>./Cid.cpp</file>
<line>827</line>
<text>Can not deploy content of domain mydomain.tld</text>
- <message code="Cannot unpack" severity="error">
<text>unknown error</text>
</message>
</message>
</object>

It´s Plesk 9.3 on Suse 11.1

regards
Wolfgang
 
Try to find related error messages in migration.log from /usr/local/psa/PMM/... and post it here.
 
Hello Igor,

I updated the Migration Agent as discribed and could connect to my Confixx 3.3.3 Server from Plesk 9.3.
But during the migration i get the following Error:

<?xml version="1.0"?>
<execution-result status="error"><message code="InternalDtdValidationFailed" severity="error"><context>void plesk::validateSchema(plesk::tXmlDocument&amp;, const std::string&amp;)</context><file>./xml_parse.cpp</file><line>412</line><text>Failed validation of the document with its internal DTD. The errors are: Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'mailuser-permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'mailuser-permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed..</text></message></execution-result>

I also tried the FIX Article ID: 7021

same Problem. any Ideas.

Thanks Lars
 
migration.log - The error-part

Hi Igor,

here is the part of the migration-log where code 1 occures.

regards
Wolfgang


[20:33:24|DEBG: 6994:p.Ssh] Execution finished with return code 0
[20:33:24|DEBG: 6994:p.libssh2pp.Channel] Closed
[20:33:24|DEBG: 6994:p.Ssh] Reading data to the file /usr/local/psa/PMM/var/20100301202813306/resellers/res0/web11/subdom.domain03.de/web_subdom.domain03.de_vhost_1002012033.tar
[20:33:24|DEBG: 6994:p.Ssh] Reading data from the remote file /migration/20100301202813306//resellers/res0/web11/subdom.domain03.de/web_subdom.domain03.de_vhost_1002012033.tar
[20:33:24|DEBG: 6994:p.Ssh] Executing cat /migration/20100301202813306//resellers/res0/web11/subdom.domain03.de/web_subdom.domain03.de_vhost_1002012033.tar on the remote host
[20:33:24|DEBG: 6994:p.libssh2pp.Session] Opening SSH channel for command 'cat /migration/20100301202813306//resellers/res0/web11/subdom.domain03.de/web_subdom.domain03.de_vhost_1002012033.tar'
[20:33:24|DEBG: 6994:p.Ssh] Execution finished with return code 1
[20:33:24|DEBG: 6994:p.libssh2pp.Channel] Closed
[20:33:24|DEBG: 6994:p.Ssh] Executing sh -c cd\ /migration/20100301202813306/\;\ rm\ /migration/20100301202813306//resellers/res0/web11/subdom.domain03.de/web_subdom.domain03.de_vhost_1002012033.tar on the remote host
[20:33:24|DEBG: 6994:p.libssh2pp.Session] Opening SSH channel for command 'sh -c cd\ /migration/20100301202813306/\;\ rm\ /migration/20100301202813306//resellers/res0/web11/subdom.domain03.de/web_subdom.domain03.de_vhost_1002012033.tar'
[20:33:24|DEBG: 6994:p.Ssh] remote stderr -> rm: cannot remove `/migration/20100301202813306//resellers/res0/web11/subdom.domain03.de/web_subdom.domain03.de_vhost_1002012033.tar': No such file or directory

[20:33:24|DEBG: 6994:p.Ssh] Execution finished with return code 1
[20:33:24|DEBG: 6994:p.libssh2pp.Channel] Closed
[20:33:24|DEBG: 6994:p.Ssh] Reading data to the file /usr/local/psa/PMM/var/20100301202813306/resellers/res0/web11/thedomain02.de/web_thedomain02.de_vhost_1002012033.tar
[20:33:24|DEBG: 6994:p.Ssh] Reading data from the remote file /migration/20100301202813306//resellers/res0/web11/thedomain02.de/web_thedomain02.de_vhost_1002012033.tar
[20:33:24|DEBG: 6994:p.Ssh] Executing cat /migration/20100301202813306//resellers/res0/web11/thedomain02.de/web_thedomain02.de_vhost_1002012033.tar on the remote host
[20:33:24|DEBG: 6994:p.libssh2pp.Session] Opening SSH channel for command 'cat /migration/20100301202813306//resellers/res0/web11/thedomain02.de/web_thedomain02.de_vhost_1002012033.tar'
[20:33:24|DEBG: 6994:p.Ssh] Execution finished with return code 1
[20:33:24|DEBG: 6994:p.libssh2pp.Channel] Closed
[20:33:24|DEBG: 6994:p.Ssh] Executing sh -c cd\ /migration/20100301202813306/\;\ rm\ /migration/20100301202813306//resellers/res0/web11/thedomain02.de/web_thedomain02.de_vhost_1002012033.tar on the remote host
[20:33:24|DEBG: 6994:p.libssh2pp.Session] Opening SSH channel for command 'sh -c cd\ /migration/20100301202813306/\;\ rm\ /migration/20100301202813306//resellers/res0/web11/thedomain02.de/web_thedomain02.de_vhost_1002012033.tar'
[20:33:24|DEBG: 6994:p.Ssh] remote stderr -> rm: cannot remove `/migration/20100301202813306//resellers/res0/web11/thedomain02.de/web_thedomain02.de_vhost_1002012033.tar': No such file or directory

[20:33:24|DEBG: 6994:p.Ssh] Execution finished with return code 1
[20:33:24|DEBG: 6994:p.libssh2pp.Channel] Closed
[20:33:24|DEBG: 6994:p.Ssh] Reading data to the file /usr/local/psa/PMM/var/20100301202813306/resellers/res0/web11/thedomain01.de/web_thedomain01.de_vhost_1002012033.tar
[20:33:24|DEBG: 6994:p.Ssh] Reading data from the remote file /migration/20100301202813306//resellers/res0/web11/thedomain01.de/web_thedomain01.de_vhost_1002012033.tar
[20:33:24|DEBG: 6994:p.Ssh] Executing cat /migration/20100301202813306//resellers/res0/web11/thedomain01.de/web_thedomain01.de_vhost_1002012033.tar on the remote host
[20:33:24|DEBG: 6994:p.libssh2pp.Session] Opening SSH channel for command 'cat /migration/20100301202813306//resellers/res0/web11/thedomain01.de/web_thedomain01.de_vhost_1002012033.tar'
[20:33:24|DEBG: 6994:p.Ssh] Execution finished with return code 1
[20:33:24|DEBG: 6994:p.libssh2pp.Channel] Closed
[20:33:24|DEBG: 6994:p.Ssh] Executing sh -c cd\ /migration/20100301202813306/\;\ rm\ /migration/20100301202813306//resellers/res0/web11/thedomain01.de/web_thedomain01.de_vhost_1002012033.tar on the remote host
[20:33:24|DEBG: 6994:p.libssh2pp.Session] Opening SSH channel for command 'sh -c cd\ /migration/20100301202813306/\;\ rm\ /migration/20100301202813306//resellers/res0/web11/thedomain01.de/web_thedomain01.de_vhost_1002012033.tar'
[20:33:25|DEBG: 6994:p.Ssh] remote stderr -> rm: cannot remove `/migration/20100301202813306//resellers/res0/web11/thedomain01.de/web_thedomain01.de_vhost_1002012033.tar': No such file or directory

[20:33:25|DEBG: 6994:p.Ssh] Execution finished with return code 1
[20:33:25|DEBG: 6994:p.libssh2pp.Channel] Closed
[20:33:25|DEBG: 6994:p.Ssh] Reading data to the file /usr/local/psa/PMM/var/20100301202813306/dump.xml
[20:33:25|DEBG: 6994:p.Ssh] Reading data from the remote file /migration/20100301202813306//dump.xml
[20:33:25|DEBG: 6994:p.Ssh] Executing cat /migration/20100301202813306//dump.xml on the remote host
[20:33:25|DEBG: 6994:p.libssh2pp.Session] Opening SSH channel for command 'cat /migration/20100301202813306//dump.xml'
[20:33:25|DEBG: 6994:p.Ssh] Execution finished with return code 0
[20:33:25|DEBG: 6994:p.libssh2pp.Channel] Closed
[20:33:25|DEBG: 6994:p.Ssh] Executing sh -c cd\ /migration/20100301202813306/\;\ rm\ /migration/20100301202813306//dump.xml on the remote host
[20:33:25|DEBG: 6994:p.libssh2pp.Session] Opening SSH channel for command 'sh -c cd\ /migration/20100301202813306/\;\ rm\ /migration/20100301202813306//dump.xml'
[20:33:25|DEBG: 6994:p.Ssh] Execution finished with return code 0
[20:33:25|DEBG: 6994:p.libssh2pp.Channel] Closed
[
 
I have requested developer's assistance regarding these errors. I will update thread with any useful information as soon as I receive it.
 
Hi Igor,

I'm migrating 10 domains from plesk 9.3.0 to plesk 9.3.0 and I get the error with "virtual void plesk::DomainVHostRefferred::Extract" on only one of my domains.

This domain hosts a wordpress blog with plugins. The data are all extracted, but when I go the the plugins manager in wordpress, it says the files are not present. Totally strange issue. Path is correct, files are present, permissions are identical as on the source server, but once the migration done, it is like if the path was not recognized anymore...
 
How Long does the development take?

Hi,

can you evaluate how long it takes until an update will be released?

many thanks
Wolfgang
 
Unfortunately, developer who deals with this problem, is very busy now. Plesk 9.5.0 version release will be very soon. I have transferred your question to him and I hope he will take up the issue very soon.
 
Hi!
I know some way to fix this issue.

ERROR:
<object name="xxxcom231" type="client">
- <object name="dasdaad.com" type="domain">
- <object name="dasdaad.com" type="hosting">
- <message code="CantUnpackDomainContent" severity="error">
<context>virtual void plesk::DomainVHostRefferred::Extract(plesk::ContentUnpacker&)</context>
<file>./Cid.cpp</file>
<line>827</line>
<text>Can not deploy content of domain dasdaad.com</text>
- <message code="tRepository::StreamError" severity="error">
<text>Archiver error: from /usr/local/psa/PMM/var/20100427190922258/clients/xxxcom231/domains/dasdaad.com/backup_dasdaad.com_vhost_1004271909.tar to /var/www/vhosts/dasdaad.com:</text>
</message>


try unpack created tar manually.

# cd /var/www/vhosts/dasdaad.com
# tar -xvvvf /usr/local/psa/PMM/var/20100427190922258/clients/xxxcom231/domains/dasdaad.com/backup_dasdaad.com_vhost_1004271909.tar

See error what it's get you. usually it's quota error.
It's can be fixsed with
# edquota <name_of_ftp_user>
and check limits. (0 = Unlimited)
then try unpack it again.

but sometimes it's errrors can be more interesting for example I get:
tar: Error exit delayed from previous errors
then I check logs above of this error and find that "tar: httpdocs/test: Cannot open: File exists"
So, customer create file test in his httpdocs but, folder test already exists in httpdocs by template.
Solve: rename file to test.html and inform customer. or remove test folder and unpack .tar again.
 
From developers:
>>Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.

This is an existed bug in agent.include.pl from 'shared' dir. But it was fixed for new PMM agents, i.e. 'shared' dir from Confixx_Plesk9_agent.tar.gz contains fixed agent.include.pl.

Seems like not all files was overwritten in 'shared' dir. Thus rty to remove 'shared' dir and re-extract it from Confixx_Plesk9_agent.tar.gz.
Click to expand...
 
Latest version of Confixx agent for Plesk 9 in attach.
 

Attachments

  • Confixx_Plesk9_agent.tar.gz
    193.2 KB · Views: 18
Tried it under Plesk 9.2, 9.3, 9.4

Hello all,

i tried the migration with Version 9.2 and with 9.3 as well as 9.4.
With the original Migration Manager, result is as follows:


<?xml version="1.0"?>
<execution-result status="error"><message code="InternalDtdValidationFailed" severity="error"><context>void plesk::validateSchema(plesk::tXmlDocument&amp;, const std::string&amp;)</context><file>./xml_parse.cpp</file><line>412</line><text>Failed validation of the document with its internal DTD. The errors are: Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'mailuser-permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'mailuser-permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed.Element 'permission', attribute 'allowed': The attribute 'allowed' is not allowed..</text></message></execution-result>

With the Migration Manager that Igor posted, error changed like this:

<?xml version="1.0"?>
<execution-result status="success"><message code="FailedClientDeployment" severity="error"><context>void plesk::ClientDeployer::deployClientData(plesk::XmlNode) const</context><file>./client_deploy.cpp</file><line>96</line><text>Failed deployment of client res1</text><message code="ExecCliGate::InternalServerError" severity="error"><context>void plesk::CliExec::analyzeResponse()</context><file>./cmd_exec.cpp</file><line>169</line><text>Internal server error: &lt;cli&gt;&lt;failure&gt;Internal error: [Account::getPassword] can't decrypt password to be plain.&lt;/failure&gt;&lt;/cli&gt;
</text></message></message></execution-result>

Migration is still not possible.
Can someone tell me if it's working under 10.0 or 10.1.
It's getting more and more Urgent as the Problem exists for nearly a year.
any help is appreciated.


Thanks, Lars
 
Yes, it is known problem with password decrypting and developers are working on it. I will update this thread with results of investigation as soon as I receive it.
 
also a 9.5.4 to 9.5.4 migration fails with these errors:

<message code="ExecCliGate::InternalServerError" severity="error">
<context>void plesk::CliExec::analyzeResponse()</context>
<file>./cmd_exec.cpp</file>
<line>169</line>
<text>Internal server error: <cli><failure>Internal error: [Account::getPassword] can't decrypt password to be plain.</failure></cli></text>

It's very frustrating when migrating a lot of domains. Is there a workaround for this?
 
Yes, it is known problem with password decryption and developers are working on it. I hope it will be fixed soon.
 
You must log in or register to reply here.

Similar threads

N
Question Migrate mail server from other server
Replies
3
Views
399
Kaspar@Plesk
Kaspar@Plesk
T
Issue Migration fail - mailbox folder with ampersand &
Replies
1
Views
398
Kaspar@Plesk
Kaspar@Plesk
F
Question Plesk Migrator Error: Access denied for user 'admin'@'127.0.0.1' (using password: YES)"
Replies
7
Views
621
Sebahat.hadzhi
Sebahat.hadzhi
defcon8
Issue Mailbox content scrambled after migration from cPanel
Replies
5
Views
1K
Peter Debik
P
S
Apache does not apply .htaccess directives for certain files after migration through Plesk Migrator
Replies
2
Views
651
NewGate
N
Back
Top