• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Replacing a replaced installation of PHP

PeterZw

New Pleskian
Dear Parallels forum,

when we wirst started using Plesk (currently 9.5.3) a few years ago, we needed an updated installation of PHP, which was not supplied by Plesk or CentOS at the time.

So we installed it using 3rd party repositories and updated it a few times since then.

A few weeks ago I noticed that Plesk's autoinstaller has an option to install PHP 5.3.
My question: Is there any risk-free way to get back to a PHP installation maintained by Plesk? If so: How would I have to go about that? Can I just run the 5.3 installation of the autoinstaller although I already have 5.3 installed by 3rd party repositories?
 
I think that you shouldn't do something with PHP if all works fine already with your custom PHP installation.
 
Back
Top