Upgrade Advice
We are currently running WHM/cPanel 102.0.33 as it was the LTS version, and we are aware that support for it is coming to an end with the new LTS version being 110. Can you confirm if any further updates will be released for 102?
I would also like to get some advice on the upgrade process to 110 as I am aware that downgrading is not possible. For this reason, we don't have automatic updates enabled and usually take a cautious approach, upgrading incrementally.
If we were to take the incremental path, I believe we will need to go through 104, 106, 108 and finally 110. There are quite a lot of versions in each this time so we may skip some of them. I am aware that we could go directly from 102 to 110 but this frightens me with so many changes between the versions and no way to downgrade. We really don't want to break our PHP, MySQL or Exim (this is critical as we use it to send emails) versions and if something does go wrong, we would like to have a good idea which version caused it, hence the incremental approach.
Our current server configuration is the following:
- CentOS 7.9.2009
- PHP 7.4
- MySQL 5.7.42
- WHM 102.0.33
-
Hey there! Once the new version is moved to LTS, which happens every June, the previous version is no longer supported and will not have any updates. As far as the upgrade, you'll be going straight to 110 as the versions in between are no longer supported and can't be downloaded from cPanel. Version 110 is the last version that supports CentOS 7, so you'll want to think about moving to a newer system sooner than later, but there won't be any issues with the PHP or MySQL version. Since you already know they are out of date, working to get that software moved to more modern versions will be required for the next LTS update, or any future updates. 0 -
Thanks for your reply, As far as the upgrade, you'll be going straight to 110 as the versions in between are no longer supported and can't be downloaded from cPanel.
We normally edit /etc/cpupdate.conf to a specific version such as the following and I seem to remember doing something like this for the intermediate versions last time we changed LTS (but I could be wrong): CPANEL=11.104.0.0 RPMUP=manual SARULESUP=manual STAGING_DIR=/usr/local/cpanel UPDATES=manual As I said, it seems like quite a big jump to go from 102 to 110 in one go if there is no way back.Version 110 is the last version that supports CentOS 7, so you'll want to think about moving to a newer system sooner than later, but there won't be any issues with the PHP or MySQL version. Since you already know they are out of date, working to get that software moved to more modern versions will be required for the next LTS update, or any future updates.
Yes, we are aware of the CentOS 7 EOL date and updates required for PHP 8. This is part of a bigger question for us to think about. We would probably prefer to start from scratch on a new server if moving to a new OS and I have read about AlmaLinux being a successor to CentOS with longer support but we haven't looked too much into it yet.0 -
Yes, we are aware of the CentOS 7 EOL date and updates required for PHP 8. This is part of a bigger question for us to think about. We would probably prefer to start from scratch on a new server if moving to a new OS and I have read about AlmaLinux being a successor to CentOS with longer support but we haven't looked too much into it yet.
Personally, I would focus on getting off of CentOS 7 and moved over to AlmaLinux and during the process you can install a newer version of cPanel and resolve 2 issues simultaneously.0 -
There's no need to manually update to each "in between" version when doing a cPanel update. 0 -
If it helps at all, we had a number of servers update from V102 LTS to V110 LTS and there were no issues with the upgrade per-se. The "issues" you are going to run into are more support issues like: - The new theme
- Horde being gone
- Add-on's, Subdomains and aliases now all being under "Domains"
0 -
Ok, thanks for your comments. We'll have a think about it. 0
Please sign in to leave a comment.
Comments
6 comments