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

Plesk 10.4.x makes having a compiled version of php NOT USABLE ! plesk 6,7,8,9 are ok

andyb-uk

New Pleskian
Hi

I have been using Plesk in a hosting environment for over 6 years now.

One of the common things our clients ask for is a custom compiled version of PHP.

In the past I have always just compiled from source to /usr/local/php_apache and /usr/local/php_cgi - usually i symlink /usr/bin/php5-cgi to /usr/local/php_cgi/bin/php-cgi - this has always been fine (for years...)

With the changes in the latest version (10.4.x) the Plesk autoupdates randomly change the version of php randomly back to the original os version (thus breakiing everyone's sites !!!)

- In Debian/Ubuntu I can't hold the package (in apt) or Plesk is not able to update - it actually managed to get debian depency hell (pretty rare)
- The same occurs in Centos btw (with plesk 10.4.x)

To try to combat this I am now atempting to make ubuntu 8.04 debian packages of php 5.3.10 (for example) - this would 'fix' the issue as the version number will be higher that the version in the OS so it will not automatically updated (as its a higer version number) - this is however a far far far more complex task than just compiling from source...

For example I have an ubuntu8.04 server that requires the latest 5.3.x PHP - normally I would just compile from source, it would be a 30 mins job max - right now i'm on day 2 of trying to backport ubuntu 12.04 php5 packages to 8.04 - The thing is if they were runnig Plesk 9 I wouldn't need to bother creating packages (a simple source install works)

Is there an actual sane method to have a compiled version of PHP, and ensure it won't randomly change and still update Plesk ??

- Right now I am advising clients to stick with Plesk9 / use cpanel

(I should note in Cpanel its really easy to have the latest stable PHP (without breakling your server.......))

Any advice is welcomed... The standard OS version of php53 for centos is pretty old now (5.3.3) and we aqre getting requests to upgrade it constantly..
 
Last edited:
Plesk doesn’t ship client’s PHP, it only downloads it from original OS vendor repo and it is quite likely it may be outdated there (especially for older OS). If your OS comes with latest version of PHP, then Plesk would run this latest PHP for clients.
 
Hi

Thats not the point at all......

The point is that since the autoupdater features in Plesk 10.x if you have a custom compiled version of PHP it gets automatically replaced by the Plesk autoupdater (this has happened on multiple servers / different distros.... ALL were fine on Plesk 9 and below.)

This didn't happen in older versions of Plesk.

Are you saying that the autoupdater/microupdates do not replace the php binary beacuse 'something' that Plesk 10.4.x installs does...

I know you won't 'support' a compiled version of PHP, I just want to have the ability to compile my own and NOT have to randomly replaced....

Any help wouid be good - it is only Plesk (10.x) servers that I have ever seen that have this issue
 
Last edited:
For yum, add into /etc/yum.conf something like

exclude=php*
 
Hi

I have tried the equivlent in debian/ubuntu


i.e :-

echo php5 hold | dpkg --set-selections

That then causes a dependecy hell with Plesk updates....

Is there a better way?

Thank you for your quick responses.

Sorry about the tone of my email its just Plesk 9.x used to be more 'accepting' of compiled software.
 
Back
Top