• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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.

Plesk 12.5 Subdomains do not interpret PHP!

psx01de

New Pleskian
Hi,

it seems that all subdomains, which are in different Folders than subdomain.Domain.tld (e.g. from older structure /subdomains/subdomain) does not Interpret PHP since upgrade to 12.5.30#7. The source code is printed out directy, which is a huge security issue.

PHP is set to FCGI, but the other Settings (FPM) also don't work.

How to fix that?

Thanks,
Patrick
 
Hi @psx01de!

Could you please give some more information:
1. What is your OS (you can place here output of "plesk version" CLI command)?
2. What Plesk version did you use before upgrade to Plesk 12.5.30#7?
 
Product version: 12.5.30 Update #7
Update date: 2015/10/19 13:07
Build date: 2015/08/26 19:00
OS version: Ubuntu 14.04
Revision: 344620
Architecture: 64-bit
Wrapper version: 1.2

Before: 12.1.x?

It occurs only to those old subdomains which were originally created in subdomains/... (I think created in a Special Version of plesk).
 
Oh - I think I have the solution: With the Update, Apache2 changed from mpm_prefork_module to mpm_event_module and then mod_php5 is not usable anymore (because it's compiled non-threadsafe) - so all Websites using Apache PHP a Setting (Default one in earlier plesk versions) have set a non working PHP handler anymore.

I think its a bug that
a) Plesk changes the Apache Settings
b) Its possible to select a PHP handler which cannot work

Also it would be great to be able to disable non-working php handlers _AND_ change all domains which connected to this handler to a new one. (This also would be great for old SSL certificates!)
 
You're right. You will need to use the mpm_prefork_module and activate mod_php5. The same issue occurs on "web space" domains (the ones without a subscription) while ordinary domains (domain.tld) in subscriptions are seemlingly not affected.
 
Back
Top