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

Resolved PHP handlers not available in PHP settings (after Update to ONYX)

Ueli Kramer

New Pleskian
TITLE:
PHP handlers not available in PHP settings (after Update to ONYX)

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk Onyx v17.5.3_build1705170317.16 os_Ubuntu 14.04​

PROBLEM DESCRIPTION:
On the PHP settings page all PHP versions are displayed but the <select> elements are empty for "run php as" input. After changing the PHP version, the XHR request does contain an empty phphandlerid (due to empty select). The handlers are all existing using the psa command to retrieve the php handlers and looking into the database.
STEPS TO REPRODUCE:
Actually don't know because I only did an update to ONYX.​

ACTUAL RESULT:
It is not possible to make any changes to the php versions.​
 
Solved by PLESK technical support

It is a reported bug with ID PPS-581. The developers are already working on it.

As a workaround, you can do these steps:

1) I enabled the nginx web server using the below command:

++
root@:~# /usr/local/psa/admin/bin/nginxmng -e
++

2) Go to Domains >> Apache&Nginx Settings >> Enabled the nginx proxy mode.

3) After that I disabled the nginx web server using the below command:

++
root@:~# /usr/local/psa/admin/bin/nginxmng -d
++

After performing the above changes, you can see the php handlers again.
 
Hi,

Any news on when this bug will be resolved ?
I have a lot of servers and don't want to solve the issue manually on each of them with the nginx trick.

Best regards
 
Back
Top