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

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