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

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