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

internal php upgrade

JLChafardet

Regular Pleskian
Another feature i would like to see (and i know is not a hard one to implement) is internal plesk php upgrade to latest php (5.2.6).

it is really bothersome in some cases, where some network scanners (yes yes yes i know, loads of them tend to report false positives) detect plesk internal php version and show a vulnerability, this can be indeed avoided by turning off the exposure of php, but if it is possible to upgrade php why not do it?

or release a guide for us, the clients, to be able to manually compile php plesk friendly for internal plesk.
 
very nice :) thanks for the info. then i wait for 8.4.1 with open arms.... loads of bugs should be fixed for it from 8.4.0
 
lol, thanks for the tip, we have our own source compilation of php, thats a good option, i have used art rpms in the past, they rule. i still use their mysql rpms. but we were talking about internal plesk php not server wide public php ;)
 
Back
Top