Cpanel has become imposing specific systems on us

[kiopeed]

I have been working with you for 11 years and I have sites running on an old php version
And now after installing today centos-8.2-x86_64
The system says it is no longer supported
I'm installing ubuntu-20.04-x86_64
But I was surprised that it does not support old versions of PHP
What do I do after your company imposes higher versions of PHP on us?
I have old forums and websites that only work on old versions of PHP. It cannot work on modern versions. What should I do?
I'm going crazy my business will be ruined because of you
If you impose this on us, why should I do it?
Is there a solution to this disastrous problem?

 

[ffeingol]

Install on Alma 8 and then install CloudLinux. They give you a hardened version of PHP (they backport the old security patches). Alma 8 has a longer lifetime than Ubuntu 20.04.

 

[cPRex]

What @ffeignol said is correct - we don't support older PHP versions because they have known security issues. CloudLinux allows you to run those older versions in a more secure environment, so that is the safest way to run older versions of PHP on a server.

The ultimate, long-term answer, is to get the sites upgraded to work with a more modern version of PHP. Unfortunately, web development isn't a "set it and forget it" model unless you have the most basic of HTML sites. Sites using PHP will need to be updated from time to time to work with newer versions.

 

[kiopeed]

What @ffeignol said is correct - we don't support older PHP versions because they have known security issues. CloudLinux allows you to run those older versions in a more secure environment, so that is the safest way to run older versions of PHP on a server.

The ultimate, long-term answer, is to get the sites upgraded to work with a more modern version of PHP. Unfortunately, web development isn't a "set it and forget it" model unless you have the most basic of HTML sites. Sites using PHP will need to be updated from time to time to work with newer versions.

Alma 8 its work or not

 

[kiopeed]

Install on Alma 8 and then install CloudLinux. They give you a hardened version of PHP (they backport the old security patches). Alma 8 has a longer lifetime than Ubuntu 20.04.

thank you sir

 

[kiopeed]

What @ffeignol said is correct - we don't support older PHP versions because they have known security issues. CloudLinux allows you to run those older versions in a more secure environment, so that is the safest way to run older versions of PHP on a server.

The ultimate, long-term answer, is to get the sites upgraded to work with a more modern version of PHP. Unfortunately, web development isn't a "set it and forget it" model unless you have the most basic of HTML sites. Sites using PHP will need to be updated from time to time to work with newer versions.

Sir, why don't you reply? How can I do about this problem? We cannot update these additions, as the developers of some sites have stopped working for a long time.
What do we do? Please send me a replacement for this board, whose prices seemed crazy and expensive
And now impose a specific php on us
And you think the decisions you make are the right ones, and my business will be ruined because of you
Many people are working on old versions of PHP, and why are you imposing a specific PHP on us?
Please send a replacement for this board

 

[kiopeed]

We should stop using this cpanel s we look for an alternative solution. Our business has been destroyed because of you

 

[JoseDieguez]

someone already told you the solution.

use Almalinux 8 , and convert to CloudLinux, wich will allow you to use old php version.

 

[sparek-3]

You're probably wanting - at least what I call - Enterprise level hosting. Which is not really the market for cPanel.

I define Enterprise Hosting as hosting where you (the client) have a dedicated IT and programming department at your disposal.

If you're running a piece of software that requires a now end-of-life version of PHP then you need staff on your payroll that can patch code in the software when security flaws are exposed. You're just not going to find that in the shared hosting space.

The issue isn't so much the end-of-life version of PHP. The issue is the script requiring such PHP. This would be like a shared hosting provider allowing end-of-life versions of PHP so a client's Joomla! 1.5 (which went end of life in 2012) installation could continue to work. How many security flaws is the administrator of that shared hosting server exposing themselves to just to satisfy a client?

Enterprise level hosting (at least my definition) you have a much more personal relationship with the IT and support staff managing you website. With shared hosting - or even dedicated/VPS hosting - the IT and support staff that administer those servers are managing hundreds or thousands of accounts. They simply can't offer that one-on-one relationship to know everything that's going on with your website and the scripts it is built on.

Enterprise level hosting won't be cheap. But that's the cost of living if you don't want to follow standard Internet practices.

I've told people many times developing web apps (or scripts on websites) is not like developing a standalone desktop application like in the 80s, 90s, or 2000s. If an application is written to work on a desktop where the individual interfacing with the application has to be sitting at the computer/device then security of the application is not as paramount as a web based application. For a standalone desktop application, you can kind of vet who has access to the application. Random people on the street probably aren't going to walk into your house or place of business and try to find the security holes in the application while you're standing there watching them. But for web applications... do you actually know everyone that's accessing your application? If it's on the web, it's pretty much open to everyone. You might password protect it or wall it off to certain individuals, but who's to say that someone dedicated enough couldn't find a way around that? And often times that's not the intent for web based applications - especially forums (imagine if cPanel blocked off access to this forum and only allowed paying members to have access to it).

Web based applications and scripts are akin to livable entities. The ecosystem around them is ALWAYS changing and the application/script has to change to keep up. A standalone desktop application that's written for OS/2 Warp will continue to work as long as you have an OS/2 Warp system down in the basement.

That's why the security of web applications and scripts is so important. If the script you are using is requiring an end-of-life version of PHP to work... then that script has long since been abandoned by it's developers. If it's not been abandoned, then you need to ask the developer of the script why the script hasn't been updated to work with modern PHP versions.

 

[kiopeed]

someone already told you the solution.

use Almalinux 8 , and convert to CloudLinux, wich will allow you to use old php version.

Is there an online explanation for this

 

[cPRex]

Security Features under the "Hardened PHP" section: Features - CloudLinux

 

[bellwood]

This thread makes me giggle.

While I understand it's not in everyone's bailiwick to be a developer/sysadmin, know best practices and delegates these things to others, your applications and digital presence is no different than owning and operating EVERYTHING else.

All things need to be maintained and updated.

cPanel does nothing but provide an interface to underlying software. They age out what they support as the upstreams deprecate.

Cent OS 8 End-of-Life Announcement | cPanel Blog

cPanel response to Cent OS 8 reaching end-of life.

blog.cpanel.com

PHP: Unsupported Branches

www.php.net

I would be looking to contract a PHP developer to upgrade and modernize your sites and then put a plan in place to ensure you don't fall behind.

Sure, you could pay more for CloudLinux and re-install the outdated software, but, you're just delaying the inevitable. If your business can be *ruined* by something as simple as aging software, then, that sounds like something that needs to be brought up with your team during SWOT and addressed, like, immediately.

 

[ttremain]

Our business has been destroyed because of you

The problem is your code. If you drove a car that required a specific fuel or additive that hasn't been produced for 30 years, then it's YOUR issue, not the fault of the fuel station down the street that won't/can't supply this for you.

Fix your code so it can run on more current and secure O/S, or piece together your own LAMP environment and stop blaming cpanel for not staying 100% backwards compatible with your outdated codes.

They are not destroying your business, you are.

You can't just setup and forget unless you are running a specific LAMP environment for that website. Even then I don't recommend it.

You can update the site, or put it on a server that never has to be updated? I don't recommend the later. Currently your developers retired, eventually anyone who knows that old PHP will retire too. Then you'd REALLY be stuck. I'd fix it now while you can.

The CloudLinux solution still just buys you time.