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

Forwarded to devs Migrating domain ends up with php error

tkalfaoglu

Silver Pleskian
TITLE:
Migrating domain ends up with php error
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
PLESK Onyx latest version, Centos 6.9 to Centos 7.5
PROBLEM DESCRIPTION:
Because older PHP is no longer supported, a migrated domain using older PHP versions cause the following problem after migration..

AH00526: Syntax error on line 22 of /var/www/vhosts/system/kalfaoglu.com/conf/vhost.conf: Invalid command 'php_admin_flag', perhaps misspelled or defined by a module not included in the server configuration.
STEPS TO REPRODUCE:
Migrate a domain from an older server to a newer server, both running Onyx -- a domain that uses an older PHP​
ACTUAL RESULT:
PHP error when logging in to plesk: cannot create apache files.​
EXPECTED RESULT:
smooth sailing. beer afterwards.​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Help with sorting out
 
Last edited:
Unfortunately provided steps to reproduce are not enough. More detail is needed about configuration of source server, target server and domain on the source server. Also, provided error not looks as migration error.
 
If my guess is correct, your old server is using Apache php handler and new server it will be fastcgi one. In my opinion, I guess two fix will be there.

1. Check all vhosts.conf in old server and remove entries starting from "php_admin_flag'" and rebuild entire apache vhosts using httpdmng utility. and then start migration again.

2. Second option you can try is change the default apache handler in new server to Apache handler and install same old php version and make it default and then once migration is completed, then you can change the default php version if needed .

How to change PHP handler in all Service Plans
How to set another default PHP version for new subscriptions?

Please share more details like old server php version, plesk version, php handler which is used (apache/fastcgi) etc and same details that in the new server as well.
 
Back
Top