Important Plesk Migrator extension

[Alina Dmi]

Plesk Migrator 2.8

What`s new:

• [+] When importing sites, databases, or directories, the actual status of each item is displayed. If import of an item failed or generated a warning, a detailed list of issues is available.
• [-] Removing an additional domain that was previously imported from another server resulted in an error in Plesk panel. (PMT-3701)
• [-] In case of a database name or database user name conflict during site import, if there were additional spaces between the names and values of corresponding variables in the wp-config.php file, the WordPress application did not work after import. (PMT-3673)
• [-] Passwords for accounts with names, containing Unicode characters outside of ASCII range, could not be decrypted after migration. (PMT-3667)
• [-] If the source FTP server did not support TLS, this negatively affected the performance during import site. (PMT-3643)
• [-] When migrating from Plesk Onyx, an error in decrypting a password for an account could result in resetting passwords for all accounts. (PMT-3604, PMT-3605)
• [-] Extension data on the target server could be overwritten by data from the source server. Now by default the server-wide extension settings are not migrated. (PMT-3586)
• [-] Overuse policy for reseller accounts was not migrated and instead was reset to 'Overuse of disk space and traffic is allowed'. (PMT-3469)
• [-] Database import failed if the PHP process had no write permission on the source server. (PMT-3682)
• [-] Copying a MySQL database from Plesk Onyx on a Linux server failed if the database server password was stored in plain text format. (PMT-3759)
• [-] Protected directories on subdomains were not migrated from DirectAdmin. (PMT-3764)
• [-] When using PureFTD on the source server, the site import performance was lower than expected. (PMT-3679)
• [-] Under certain circumstances, migration from a Plesk for Linux server could fail with an error message "Cause: 'int' object has no attribute 'isdigit'". (PMT-3621)
• [-] SSL Certificate Authority certificates were not migrated from DirectAdmin. (PMT-3613)
• [-] When migrating mail messages to Plesk for Linux via IMAP, if a mailbox name contained an uppercase character, the messages in it were not migrated. (PMT-3607)
• [-] When migrating from DirectAdmin, a cron task with a certain syntax could not be parsed. (PMT-3544)
• [-] When migrating from DirectAdmin, if a mailbox had an automatic reply set up, but the corresponding template file did not exist, the migration could not be performed. (PMT-3542)
• [-] When migrating from or to a Plesk server with a remote SmarterMail server: the type 'A' DNS records for mail (mail.*) were migrated incorrectly. (PMT-3725)
• [-] When migrating from Plesk with a remote SmarterMail server to Plesk with a local SmarterMail server, or vice versa, the webmail settings for hosting plans and subscriptions were not converted as intended. (PMT-3723)

 

[Alina Dmi]

Plesk Migrator 2.9

What`s new:

• [+] An option to migrate a reseller with all accounts and subscriptions has been implemented.
• [+] Now when a subscription, owner or subscription plan is already migrated, it can be hidden from the 'List of subscriptions' tab.
• [+] When migrating from cPanel, there is an option to choose whether to migrate subdomains and domain aliases as addon domains, thus preserving the related email accounts.
• The DirectAdmin migration agent now checks the data consistency on the source side. It correctly performs migration even when there are errors in the configuration of some domains. The overall fault tolerance of the agent has been improved.
• The 'List of subscriptions' tab was added to the migration screen. It replaces the 'Add subscriptions' tab in simple mode, or the 'Subscriptions list' tab in advanced mode.
• [-] When migrating sites from cPanel, the Plesk Migrator detected a single WordPress instance as two separate instances. (PMT-3672)
• [-] MySQL events were not transferred during migration. (PMT-3677)
• [-] In certain circumstances it was impossible to import a website, if its webspace had files with names, containing non-ASCII characters. (PMT-3703)
• [-] Now, if the target database has earlier version and does not support some features of the source database, a comprehensive message is shown at the end of migration. (PMT-3241)
• [-] MySQL databases could not be migrated if a database's admin password did not match the password stored in the PSA database. (PMT-3778)
• [-] Migration of mail content from cPanel failed, if the home directory on source was different from /var/home/ (PMT-3212)
• [-] Several domain aliases, created by cPanel for internal purposes, were migrated as domain aliases in Plesk. Now Plesk Migrator recognizes and ignores such technical aliases. (PMT-3506)
• [-] Plesk Migrator did not set a password for the source server's user that it creates for copying content. Some servers' configurations forbid SSH authorization of such users, thus making copying unavailable. (PMT-3558)
• [-] Additional Apache and nginx directives of subscriptions were not transferred. (PMT-3072)

 

[Alina Dmi]

Hi all,
Next version of Plesk Migrator(2.11) has been released just now!

Changes:

• [+] Plesk Migrator now supports importing websites with Joomla, Drupal, and Prestashop installed (with certain limitations, to learn more, read Migration Guide for details).
• [+] Users can now view the migration log in real time and search the log for key phrases in the Plesk Migrator interface.
• The reliability of migrations from servers with non-English locale has been improved.
• [-] Re-syncing a subscription that was reassigned to a different owner during migration flooded the migration log with PHP notices, and could corrupt the Plesk Migrator interface if the display_errors PHP option was enabled. (PMT-3887)
• [-] Migration from Plesk failed if one or more customer passwords on the source server decrypted to 'none'. (PMT-3876)
• [-] When migrating from Ubuntu or Debian to CentOS or RedHat Enterprise Linux (or vice versa), subscriptions with files owned by the web server that contained non-UTF-8 characters could be assigned to incorrect owners. (PMT-3860)
• [-] Migration could not be started if one or more secret keys in the Plesk database could not be decrypted correctly. (PMT-3298)
• [-] When migrating from Helm via the command line, the shallow-dump.xml file was created anew during each migration stage, which considerably prolonged the migration. (PMT-3921)
• [-] Migration from Helm failed if one or more packages had enabled features whose parent plan was deleted. (PMT-3912)
• [-] The post-migration report did not contain information about missing DNS records for domains whose names contained IDN characters. (PMT-3906)
• [-] Migration from Helm failed if one or more identical IP addresses were registered as both shared and dedicated on the source server. (PMT-3878)
• [-] Under specific circumstances, copying of mail content for individual mailboxes could fail. (PMT-3868)
• [-] Copying of mail content could fail when migrating MailEnable accounts with a large number of mails. (PMT-3866)
• [-] On servers with the Chinese locale, under specific circumstances, syncing Microsoft SQL Server databases could result in an error. (PMT-3832)
• [-] Migration from a server with Japanese locale could fail with a misleading error message when copying website content. (PMT-3705)
• [-] When importing an application to Plesk for Windows, the import could fail if the application had an exceedingly large number of files. (PMT-3975)
• [-] Plesk Migrator could not set the correct permissions for statistics and logs directories. (PMT-3934)
• [-] Migration from Plesk failed if MariaDB 10.0.32 or later was installed on the source server. (PMT-3916)
• [-] When migrating a subscription with Magento installed, the Magento configuration file was not updated if the Magento database was renamed during migration. (PMT-3513)
• [-] When migrating a subscription with Prestashop, the Prestashop configuration file was not updated if the Prestashop database was renamed during migration. (PMT-3520)
• [-] When importing an application, the contents of all application files were lost if the specified domain name belonged to a domain already hosted on the target server. (PMT-3967)

 

[Alina Dmi]

Plesk Migrator 2.12

What`s new:

• [+] Now you can run pre-migration checks in the advanced migration mode. Successfully passing all checks automatically starts a migration.
• Performance of scanning source server contents before importing sites has been drastically improved.
• [-] When preparing for a site import, one of the applications being unavailable resulted in failure to detect other applications and list them on the site import page. (PMT-4061)
• [-] When transferring a subscription from Plesk Onyx, only a single scheduled task was transferred to the target server. (PMT-3894)
• [-] When migrating a subscription from Plesk 11.5 or later, the password for site application database was not decrypted on the target server, which resulted in the application unable to work on the target server. (PMT-4026)
• [-] When migrating from a Linux server with Plesk Onyx, pre-migration checks did not detect it when the webmail, used on the source server, was missing on the target server. (PMT-3145)
• [-] A component, required by Plesk Migrator, was not bundled with it but instead downloaded before first site import. This could result in migration failure in case of network problems. Now the component is a part of Plesk Migrator and does not require separate downloading. (PMT-3735)
• [-] When migrating from Plesk servers, the APS applications were transferred only as content and not registered in Plesk. (PMT-4000)
• [-] The migration process was aborted if any customer's login name did not conform to the Plesk requirements (only alphanumeric characters and -.'%_). Now subscriptions owned by such customers are skipped during the migration. (PMT-3959)
• [-] Migration to a server with administrator's id different than the default one (1) resulted in failure to repeatedly migrate subscriptions or synchronize their content. (PMT-3078)
• [-] When migrating from Confixx, each transferred SSL certificate was installed as default certificate for all domains on the IP address, which resulted in all domains using the certificate of the latest migrated domain. (PMT-4043)
• [-] When migrating a subscription with a database and ODBC DSN (Data Source Name) from Plesk for Windows of version 12.5 or later, the DSN was not migrated. (PMT-3891)
• [-] Migration failed from a server having IP addresses with netmask set in short notation. (PMT-4048)
• [-] When migrating a subscription with web.config containing non-ASCII characters from a server with .NET 2.0 or 3.x to a server with only .NET 4.x, adjusting the web.config to the target server failed. (PMT-4029)

 

[Alina Dmi]

Hi all,
Plesk Migrator 2.14 has been released just now!
What`s new:

• [+] Added the ability to connect to the source server via SSH and to use rsync for importing files.
• Increased data transfer speed during website migration.
• Added the ability to generate the configuration file for command line migration by running the plesk-migrator configure command.
• On Windows servers added the ability to specify the path to the Microsoft SQL Server temporary directory by specifying the remote-mssql-session-dir option in the configuration file.
• [-] Fixed the issue where MySQL events and stored routines were not migrated. (PMT-4065)
• [-] Fixed the issue where migration failed if a user's password contained non-Unicode characters and the Enhanced security mode was disabled on the source server. (PMT-4103)
• [-] Fixed the issue where, if during a failed migration attempt a subscription's limits were not set correctly on the target server, Plesk Migrator did not try to update them during subsequent attempts. This could result in addon domains or subdomains belonging to the subscription not being migrated. (PMT-4066)
• [-] Fixed the issue where post-migration checks could sometimes stall when checking the migrated websites' pages. (PMT-4095)
• [-] Fixed the issue where website migration from servers with vsftpd installed was impossible if FTPS support was not configured for it. (PMT-4130)
• [-] Fixed the issue where Plesk Migrator occasionally failed when migrating multiple subscriptions to Plesk for Windows at once. (PMT-4170)
• [-] Fixed the issue where, if the document root directory contained there a directory with no "read" permissions, the path to the document root directory had to be specified manually. (PMT-4184)
• [-] Fixed the issue where, if the hosting description file was written in YAML, the number of domains to be migrated was very high, and multiple subscriptions were being migrated at once, migration could fail due to Plesk Migrator running out of memory. (PMT-4132)
• [-] On Linux servers fixed the issue where databases could not be migrated during website migration if the /var/www/ directory was mounted to a different partition on the target server. (PMT-4128)
• [-] On Linux servers fixed the issue where databases could not be migrated during website migration if on the target server a remote MySQL server was configured as the default database server. (PMT-4199)
• [-] On Windows servers fixed the issue where migrating content via rsync could be interrupted (for example, due to network connectivity issues or packet loss), which resulted in the migration stalling. (PMT-4163)
• [-] On Windows servers fixed the issue where files and folders with names containing national characters were not migrated during website migration. (PMT-3706)
• [-] On Windows servers fixed the issue where website migration could not start if a directory containing a symbolic link to itself was present on the source server. (PMT-4200)

 

[mr-wolf]

Plesk must have some issues with dates as no fix for either PPPM-6333 and PMT-4051 has been implemented.
Another one, PPPM-7598 hasn't been fixed either..

The PMT-4051 messes up the "setup date" of a subscription. That one isn't that of an issue for me anymore as I don't need to migrate those any time soon.
The PPPM-6333 is much more serious IMHO as it "mutilates" the website by changing all the filedates.
I even had an Apple mail client reacting on those dates (it messes up the file dates of the message files as well).

Some PHP-settings are also lost on migration. At least short_open_tag becomes a victim.
Others may get lost too, but aren't as obvious. A site that needs short_open_tag doesn't work at all, so it's fairly easy to notice.
I can see that PHP-setting lost on more occasions than only upon migration, so this probably needs more work,

Without those fixes I can never be sure that my client will not notice that something happened.

 

[mr-wolf]

Today I needed to restore a site from a back-up
All the dates of the files are set to today....
All historical data pertaining these files are lost.....

How can this NOT get fixed immediately????
Why why why???
This mutilation should have top priority, but nothing is being done.....

 

[ChristophRo]

Somehow the Plesk Migrator just screwed us over by going into a mode of only doing only one single subscription migration at a time.
Normally - and we testet that several times - it does like 6-8 at once and we were able to perform the complete server migration in a couple hours.

But now, when we had/have to perform the migration fo real, it's "broken" and we most likely need to cancel the whole task, as it would take like 2 days at the current speed

Would there by any way to increase the limit of parallell running tasks/migrations anyway? We've got plenty of resources (CPU, RAM, IOPs, Network) to handle more than the default 6-8, and thus increase the migration speed.

 

[ChristophRo]

As our first/initial migration completed successfully and now all we really want is to just re-sync the database, webcontent and emails, does anyone have any experience with a "manual" synchronisation of the Plesk mail and webfolder structure?

Couldn't we just run a pretty simple rsync command over /var/qmail/mailnames/* and /var/www/vhosts/* (excluding the plesk "system" directories) and let "plesk repair fs -y" fix the possible ownership and permission problems that may occure this way?

 

[moswak]

Hi,
we transfer many accounts from confixx to plesk. this usually works very well, but a question has arisen that, should there be a solution to save some time.

the migrator sets all migrated domains to php7.3-fpm.
In order for the site to work for old customers we set the php version of the original server after the migration for all domains. (For example: / usr / local / psa / bin / php_handler --replace -old-id plesk-php73-fpm -new-id plesk-php54-fastcgi)
that takes a while at many domains

Is there a possibility that the php-version that the migator for migrated domains sets "before" the migration can influence?

 

[trialotto]

@moswak

In response to

Is there a possibility that the php-version that the migator for migrated domains sets "before" the migration can influence?

I can simply answer with

"yes, there is : simply install the desired PHP version before migrating"

but that "yes" is of the conditional kind : the PHP version should be supported (by the OS vendor OR by Plesk).

In your case, the older PHP version is not supported - and that might explain the problems you are encountering at migration time.

Hope the above helps a (tiny) bit.

Regards...........

 

[Hielko]

I'm trying to add the migrator extension but this gives an internal server error. Is this a firewall issue? We're using:

OS ‪Ubuntu 18.04.3 LTS‬
Product Plesk Onyx
Version 17.8.11 Update #78, last updated on Jan 9, 2020 02:09 PM

 

[Alina Dmi]

I'm trying to add the migrator extension but this gives an internal server error. Is this a firewall issue? We're using:

OS ‪Ubuntu 18.04.3 LTS‬
Product Plesk Onyx
Version 17.8.11 Update #78, last updated on Jan 9, 2020 02:09 PM

Hello!
Could you please provide us the content of panel.log?

 

[Hielko]

I found the panel.log file. The file is rather large so I'm listing the last messages in the file:

[2020-01-10 10:20:31.600] ERR [1] Operation timed out after 30000 milliseconds with 0 out of 0 bytes received
[2020-01-10 13:44:21.614] ERR [1] Operation timed out after 30000 milliseconds with 0 out of 0 bytes received
[2020-01-10 13:44:52.007] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-10 13:45:22.140] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-10 13:45:25.620] ERR [1] Operation timed out after 30000 milliseconds with 0 out of 0 bytes received
[2020-01-10 13:45:55.754] ERR [1] Operation timed out after 30000 milliseconds with 0 out of 0 bytes received
[2020-01-10 13:46:25.886] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-10 13:51:15.260] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-10 13:51:45.414] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-10 14:18:05.321] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-10 14:18:35.831] ERR [1] Operation timed out after 30000 milliseconds with 0 out of 0 bytes received
[2020-01-10 14:19:06.017] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-10 14:56:44.426] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-10 16:15:59.117] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-11 06:35:06.831] ERR [panel] Error: Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-11 06:35:41.928] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-11 10:20:31.356] ERR [panel] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received:
0: /opt/psa/admin/plib/modules/catalog/library/Http/Curl.php:41
PleskExt\Catalog\Http\Curl->request(string 'https://ext.plesk.com/api/v4/packages?with-details&platform=unix&with-hidden&locale=en-US&country=NL')
1: /opt/psa/admin/plib/modules/catalog/library/Extension/Fetcher.php:108
PleskExt\Catalog\Extension\Fetcher->getFeedContent(string 'packages', string '?with-details')
2: /opt/psa/admin/plib/modules/catalog/library/Extension/Fetcher.php:39
PleskExt\Catalog\Extension\Fetcher->getPackages(string 'packages', string '?with-details', array)
3: /opt/psa/admin/plib/modules/catalog/library/Extension/Catalog.php:145
PleskExt\Catalog\Extension\Catalog->getAvailableWithDetails()
4: /opt/psa/admin/plib/modules/catalog/library/Search/IndexManager.php:100
PleskExt\Catalog\Search\IndexManager::indexCatalogExtensions()
5: /opt/psa/admin/plib/modules/catalog/library/Search/IndexManager.php:160
PleskExt\Catalog\Search\IndexManager::indexAll()
6: /opt/psa/admin/plib/modules/catalog/scripts/update-index.php:12
[2020-01-11 10:20:31.356] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-12 06:34:54.431] ERR [panel] Error: Operation timed out after 30000 milliseconds with 0 out of 0 bytes received
[2020-01-12 06:35:25.143] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-12 10:20:31.806] ERR [panel] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received:
0: /opt/psa/admin/plib/modules/catalog/library/Http/Curl.php:41
PleskExt\Catalog\Http\Curl->request(string 'https://ext.plesk.com/api/v4/packages?with-details&platform=unix&with-hidden&locale=en-US&country=NL')
1: /opt/psa/admin/plib/modules/catalog/library/Extension/Fetcher.php:108
PleskExt\Catalog\Extension\Fetcher->getFeedContent(string 'packages', string '?with-details')
2: /opt/psa/admin/plib/modules/catalog/library/Extension/Fetcher.php:39
PleskExt\Catalog\Extension\Fetcher->getPackages(string 'packages', string '?with-details', array)
3: /opt/psa/admin/plib/modules/catalog/library/Extension/Catalog.php:145
PleskExt\Catalog\Extension\Catalog->getAvailableWithDetails()
4: /opt/psa/admin/plib/modules/catalog/library/Search/IndexManager.php:100
PleskExt\Catalog\Search\IndexManager::indexCatalogExtensions()
5: /opt/psa/admin/plib/modules/catalog/library/Search/IndexManager.php:160
PleskExt\Catalog\Search\IndexManager::indexAll()
6: /opt/psa/admin/plib/modules/catalog/scripts/update-index.php:12
[2020-01-12 10:20:31.806] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-13 06:33:02.758] ERR [panel] Error: Operation timed out after 30000 milliseconds with 0 out of 0 bytes received
[2020-01-13 06:33:33.541] ERR [1] Operation timed out after 30000 milliseconds with 0 out of 0 bytes received
[2020-01-13 10:20:31.177] ERR [panel] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received:
0: /opt/psa/admin/plib/modules/catalog/library/Http/Curl.php:41
PleskExt\Catalog\Http\Curl->request(string 'https://ext.plesk.com/api/v4/packages?with-details&platform=unix&with-hidden&locale=en-US&country=NL')
1: /opt/psa/admin/plib/modules/catalog/library/Extension/Fetcher.php:108
PleskExt\Catalog\Extension\Fetcher->getFeedContent(string 'packages', string '?with-details')
2: /opt/psa/admin/plib/modules/catalog/library/Extension/Fetcher.php:39
PleskExt\Catalog\Extension\Fetcher->getPackages(string 'packages', string '?with-details', array)
3: /opt/psa/admin/plib/modules/catalog/library/Extension/Catalog.php:145
PleskExt\Catalog\Extension\Catalog->getAvailableWithDetails()
4: /opt/psa/admin/plib/modules/catalog/library/Search/IndexManager.php:100
PleskExt\Catalog\Search\IndexManager::indexCatalogExtensions()
5: /opt/psa/admin/plib/modules/catalog/library/Search/IndexManager.php:160
PleskExt\Catalog\Search\IndexManager::indexAll()
6: /opt/psa/admin/plib/modules/catalog/scripts/update-index.php:12
[2020-01-13 10:20:31.177] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-13 12:00:35.665] ERR [1] Operation timed out after 30000 milliseconds with 0 out of 0 bytes received
[2020-01-13 12:01:06.069] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-13 12:01:36.201] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-13 12:03:31.177] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-13 12:04:01.350] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-13 14:20:58.167] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-13 14:21:28.810] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-13 14:21:59.002] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-13 14:29:09.708] ERR [1] Operation timed out after 30000 milliseconds with 0 out of 0 bytes received
[2020-01-13 14:29:39.852] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received
[2020-01-13 14:30:09.991] ERR [1] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received

 

[Alina Dmi]

Thank you for your reply!

[2020-01-13 10:20:31.177] ERR [panel] Operation timed out after 30001 milliseconds with 0 out of 0 bytes received:
0: /opt/psa/admin/plib/modules/catalog/library/Http/Curl.php:41
PleskExt\Catalog\Http\Curl->request(string 'https://ext.plesk.com/api/v4/packages?with-details&platform=unix&with-hidden&locale=en-US&country=NL')
1: /opt/psa/admin/plib/modules/catalog/library/Extension/Fetcher.php:108
PleskExt\Catalog\Extension\Fetcher->getFeedContent(string 'packages', string '?with-details')

It looks like ext.plesk.com is not available from your server. Please, open access to it.

 

[Hielko]

Thank you for your reply!



It looks like ext.plesk.com is not available from your server. Please, open access to it.

I checked the firewall rules in the new Plesk Server. Everything has the default value. Perhaps the firewall of our network is blocking it but I 'm not sure. I tried using the Plesk Installer command on Ubuntu stated in the manual but the option to select the extensions is not available.

Now I'm wondering if the new Plesk server was setup correctly. What's the correct/preferred method?

 

[Lexz]

Good morning,

We are testing the Plesk Migrator extension to move clients from DireactAdmin to Plesk.
Everything seems to work fine but database users are not migrated.
Is there a way to migrate them? Or are we doing something wrong.

Thanks in advance!

 

[Alina Dmi]

Good morning,

We are testing the Plesk Migrator extension to move clients from DireactAdmin to Plesk.
Everything seems to work fine but database users are not migrated.
Is there a way to migrate them? Or are we doing something wrong.

Thanks in advance!

Hello!
Is there any messages related to database users in migration log? What were the status of migration?

 

[Lexz]

The migration finishes successful with the status: There are no issues.
I've looked into the log and debug log but didn't find anything about the migration of the database users.

Hope you can help me. Thanks!

 

[Alina Dmi]

The migration finishes successful with the status: There are no issues.
I've looked into the log and debug log but didn't find anything about the migration of the database users.

Hope you can help me. Thanks!

We`ve confirmed a bug PMT-4746. The problem appears on mysql server(source) with version >= 5.7 (the 'Password' column of the mysql.user system table was removed in MySQL 5.7.6)

Thank you for your assistance!