• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Service plan php version conflict with hosting php version

heroman

New Pleskian
TITLE:
Service plan php version conflict with hosting php version​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Onyx 12 w/ Centos 7​
PROBLEM DESCRIPTION:
When I setup Plesk for the first time, I was asked to create a user and a domain, which I did. Once the domain was active, I changed the hosting setting to use PHP 7. The default user is automatically assigned a service plan of unlimited.

After experiencing issues with not having wddx enabled by default, Plesk support helped me to have it installed and activated. The wddx extension was visible in the php 7 settings, but would not work or show in the phpinfo for php 7.

I checked the service plan and to my surprise, the unlimited service plan had a php setting of version 5 so I changed it to 7 and synced.

wddx worked after the sync.​
STEPS TO REPRODUCE:
Set up new Plesk on Centos 7 vps from 1&1
create new domain and user
change domain hosting php setting to 7
installed php 7 extensions will not work
change service setting (unlimited) to use php 7 instead of php 5
sync​
ACTUAL RESULT:
Service setting over ride hosting setting​
EXPECTED RESULT:
Hosting setting should over ride service setting​
ANY ADDITIONAL INFORMATION:
​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug​
 
Why did not you continue to work is the scope of support ticket if the problem was not solved?
I see a case of support here, but not a bug.
 
Back
Top