• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Migration Manager broken in Plesk 12.5.30

Dree

Basic Pleskian
The migration manager seems to be rebuilt and uses the API now.
The problem is that the migration manager does not check which port Plesk is running on, and 8443 is hardcoded. Running Plesk on a different port (for security reasons) is no longer supported when using Migration Manager.

Perhaps this could be configured when starting the migration?
 
Also, the migration manager is even slower than it was before. It's hanging on this command for a very long time:

/opt/plesk/python/2.7/bin/python /usr/local/psa/admin/sbin/modules//panel-migrator/plesk-migrator generate-migration-list /usr/local/psa/var/modules/panel-migrator/sessions/20151118100919/config.ini --skip-services-checks --async
 
This seems to be due to this command on the source server:
python /tmp/panel_migrator/hosting_analyser_agent.py -f -d /var/www/vhosts -n /tmp/panel_migrator/_rsync_network_report
It looks like it's reading all vhosts on the source server, which is going to take a while for 950 GB of data.
 
The migration manager seems to be rebuilt and uses the API now.
The problem is that the migration manager does not check which port Plesk is running on, and 8443 is hardcoded. Running Plesk on a different port (for security reasons) is no longer supported when using Migration Manager.

Perhaps this could be configured when starting the migration?
Now it could be configured only when using Plesk Migrator from CLI:
you could specify "plesk-port" option in target and source server sections in configuration file.
For example:
Code:
[GLOBAL]
source-type: plesk
source-servers: pfu
target-type: plesk

[plesk]
ip: 192.168.1.1
os: unix
# Plesk panel port on the target server
plesk-port: 8448

[pfu]
ip: 192.168.1.2
os: unix
ssh-password: 123qwe
# Plesk panel port on the source server
plesk-port: 8449
 
A command line utility for Migration Manager is actually very nice!
Is there documentation for this?
 
Back
Top