• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue Migration Error

Anoop

Regular Pleskian
Server operating system version
Almalinux83
Plesk version and microupdate number
18.0.44
When try to transfer all plans or packages from one plesk server to new plesk server, its throwing some errors like

Service plan 'Standard' on source server has PHP handler
that is not installed on the target server: running in unknown mode.
Another PHP handler was selected for that service template: default Plesk handler for PHP 7.3.33 running in CGI mode
To resolve the issue, it is recommended to do one of the following:
- Install and enable such PHP handler to target server.
- Ensure that PHP handler that was selected automatically is fine for migrated web sites.
- Select appropriate PHP handler in service template once mi

So how can i solve this error
 

Attachments

  • migrate_error.jpg
    migrate_error.jpg
    191.3 KB · Views: 9
Please check which PHP version the source websites are using. Install that same PHP version through Plesk installer on the target server, then redo the migration.
 
It's just a warning. Use the latest PHP 7.x version and you should not face any problem. It's normal to have that massage during a migration
 
Can you please show the list of all PHP versions installed on the source server and a list of all PHP versions installed on the target server?
 
These are different "versions", the names don't match. It seems that you previously have installed your own PHP 7.3 and named them "alt-...". The names of these do not match the Plesk convention, hence Plesk Migrator cannot find these versions on the new server. It cannot detect that the "alt..." versions are similar or the same as the default PHP 7.3 versions that come with Plesk. It can only compare the names of the services and as the names are "wrong" on the old server, Plesk Migrator cannot match them to the new server.

You will need to update the configuration of the websites that were formerly using the "alt-..." PHP versions with the default Plesk PHP versions after migration or you need to update the websites on the source server to a standard Plesk PHP version that is named as expected.
 
Yes, it should be possible to do the migration. Migrator should select an other PHP version automatically, but that might not fit the requirements of a script perfectly, so it might need to be updated to the desired PHP version.
 
Back
Top