Resolved Plesk Migrator 12.5 to Onyx

[Steve Tozer]

Hello,

Im migrating sites over from a 12.5 server and noticed the Plesk migrator in Onyx doesn't migrate the contents of the Apache & nginx Settings section.

Wondering if this is a bug or if I have missed a setting.

 

[Alina Dmi]

Hello, Steve!
See section "What data is transferred" of https://docs.plesk.com/en-US/onyx/migration-guide/introduction.75496/
Also, additional directives are not transferred (reported as internal bug PMT-3072). It is going to be fixed in further Plesk Migrator updates.

 

[Steve Tozer]

Hello, Steve!
See section "What data is transferred" of https://docs.plesk.com/en-US/onyx/migration-guide/introduction.75496/
Also, additional directives are not transferred (reported as internal bug PMT-3072). It is going to be fixed in further Plesk Migrator updates.

Hello,

Thanks for the info that theres a bug reference already. Has this already been looked at or a work around I can do for now to make those settings migrate? I have a server im migrating in a couple of days and this means i'm going to have to add 4 lines of code into 200 domains manually.

Steve

 

[Alina Dmi]

If we are talking about workaround for additional directives I could recommend you use after migration hooks to copy missing configs. From Plesk`s side, additional directives placed into file vhost.conf which included by httpd.conf. The trick is to copy vhost.conf from source and run /usr/local/psa/admin/bin/httpdmng --reconfigure-domain <subscription>, as result httpd.conf on domain will include vhost.conf.
So, first, prepare script to copy vhost.conf(vhost_nginx.conf for nginx) into /var/www/vhosts/system/<host>/conf/ and to run /usr/local/psa/admin/bin/httpdmng --reconfigure-domain <domain_name>, the second, add after migration hook:

1. Create directory for scripts, if it does not exist yet:
mkdir -p /usr/local/psa/var/modules/panel-migrator/events/subscription-migration-finished/
2. Put prepared script to created directory and make it executable

Unfortunately, only subscription name could be processed automatically by getting first command line argument, for example:
#!/bin/sh
echo `date` $1 >> /root/finished

So, if you have a lot of subscriptions and minimal number of addons - use this workaround.
If there are a lot of addons, copy vhost.conf files manually and run /usr/local/psa/admin/bin/httpdmng --reconfigure-all

If we`re talking about data from nginx settings and Common Apache settings sections, all should be migrated without any workarounds and if it doesn`t so - let us know, we will continue investigations.

 

[DerDanilo]

@Alina Dmi
When will additional directives settings be migrated in future via the migration tool? Do you have an ETA for the bugfix?
A workarround might for for now, but it takes additional time.

This also brings up the question if additional directives settings are included into the plesk backups. Recovered several times but never actually have had to confirm that those are restored.

Thanks!

 

[Alina Dmi]

Hello!
It'll be fixed in one of the nearest updates.

 

[Alina Dmi]

Hello!
Update is available.

 

[mr-wolf]

Hey......
I had some trouble migrating some websites, but now I did these with the new migrator and they are working!!!!

 

[Alina Dmi]

Hello! Fix of problem with additional directives will be available in nearest 2-3 weeks, sorry, my mistake.

 

[mr-wolf]

I migrated some domains from a Plesk 12.5 server the day before yesterday and these websites didn't work.
They were even simple html sites.

When reading about this updated migrator I immediately installed it and tried those same domains again.

Yesterday they migrated fine (besides one).
Something must have changed for the better....

 

[Alina Dmi]

Hello!
We`ve just published update with fixed migration of additional directives, version 2.9.2