Skip to main content
cPanel Technical Support has been heavily impacted by hurricane Beryl and our ability to respond to tickets has been hindered as a result. We appreciate your understanding and patience as we address these delays.

Upgrade to Ubuntu 22.04 to get to cPanel 120

Comments

46 comments

  • cPRex Jurassic Moderator

    Hey there!  cPanel doesn't yet support in-place upgrades on Ubuntu, so the *official* answer would be to use the Transfer Tool to migrate to a newer machine.

    1
  • Alessandro Porcu

    there is an official channel in which I can follow this topic in order to understand if cPanel will release this upgrade ?

    0
  • cPRex Jurassic Moderator

    We'll likely make an announcement on our blog when this is ready, but you could also join or ELevate channel is Discord if you wanted to speak with that team directly:

    https://discord.gg/qUxJqTC5

    0
  • Alessandro Porcu

    If I read well, elevate is not an option for ubuntu installation (is not installed at the moment).

    0
  • cPRex Jurassic Moderator

    Correct

    0
  • Alessandro Porcu

    at the moment the situation is:

    root@newage:~# apt install motd-news-config
    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    Some packages could not be installed. This may mean that you have
    requested an impossible situation or if you are using the unstable
    distribution that some required packages have not yet been created
    or been moved out of Incoming.
    The following information may help to resolve the situation:

    The following packages have unmet dependencies:
     motd-news-config : Breaks: base-files (< 11ubuntu11) but 11ubuntu5.7 is to be installed
    E: Unable to correct problems, you have held broken packages.

    Motd is the last package that block the 22 upgrade.

    0
  • eitanc

    cPRex... This is VERY annoying. This is not the way to handle this.

    You, not personally, of course, as cPanel, release version 120 as "Release", and let Ubuntu pre-22  users be blocked from upgrade to 120, and then:

    1. Don't have a cPanel official blog/forum post about this move (no, sending them to discord is not legit). Telling them to wait now.

    2. Tell them no in-place upgrade of Ubuntu is supported, that they need to set up a new server and do a transfer move, which is much more risky and resource intensive, and with higher risk for failures. Not a path anyone would like to go through.

    This is very not customer friendly.

    0
  • cPRex Jurassic Moderator

    Alessandro Porcu - That type of upgrade wouldn't be related to cPanel at all, so I don't have much advice I can provide on that.

    eitanc - the developers are aware of all those concerns for sure, but I just don't have anything better to offer at this point.  It's worth noting the Transfer Tool worked fine for decades until ELevate was recently created, although it would still be nice if there were easier upgrade paths.

    0
  • eitanc

    cPRex,

    1. Maybe CP should consider defining edition channel versions per OS and not globally

    2. I think today, in the current state of software development - expecting an in-place application upgrade, after an OS upgrade, is a reasonable expectation from a software vendor.
    Forcing customers to set up a new server, tweaking it, updating it, adjusting it to its networking environment (e.g. changing IPs and nearby Firewall, etc.) and then doing the transfer process - is simply a bad way to serve customers.

    1
  • Alessandro Porcu

    In the last two years

    the cost of license of cPanel was incresead and the customer expectation in term of support is increased too. Reading the compatibility matrix all things seems to be possible but on field there is some blockers.

    If I need to spend time for moving to another server, I'll spend time to migrate to low cost solution (cpanel competitor).

    In the meanwhile 

    I'll leave open the ticket waiting for solution. 

    1
  • lbarbosapt

    We recently went through a painful migration from Cent OS 7, less than a year ago.

    In fact, the migration hasn't even been completed since there are incompatibilities from some clients on legacy software, unsupported in newer versions of cPanel, that prevent us from shutting down those machines and forcing us to keep them running (and paying those additional licenses and hosting costs). 

    At the time, in the midst of the CentOS controversy, we took a long time to decide on the OS to go with and ended up choosing Ubuntu, with one of the reasons being potentially more stability with the uncertainty around the CentOS successor.

    Before we can even shut down the machines from the previous migrations we find that our shiny new servers (less than a year is relatively new) are becoming obsolete...

    I second the previous poster in that prices have increased significantly over the past few years and it doesn't seem like we're being compensated for those increases with stability.

    Setting up new servers and migrating accounts is an additional cost imposed on your clients and not a small one.

    More care should be put into providing stability or easy upgrade paths when you make the decision not to support a version of an OS that months earlier was being recommended as an install option.

    2
  • Unnamed User

    I've got the impression that cPanel will be having only one cPanel version for the multiyear duration of each Ubuntu version - 118 for Ubuntu 20.04, 120 for Ubuntu 22.04. Maybe cPanel 122 will require Ubuntu 24.04 ?

    We need to be sure that for the effective life of a system (EOL for Ubuntu 20.04 is in 2030 and for Ubuntu 22.04 is in 2032) cPanels will continue be updated, and not reach their EOL the same day they are "born".

    I don't trust the cPanel Elevate Project because I read its "Disclaimer" section stating that "... this software could cause significant functionality failures ..." and that "We do not guarantee the functionality of software ...".

    I think it is better to stay with an operating system for the whole of its effective life. When it nears its EOL it is better to have a new system been setup separately, and gradually transfer there, instead of cPanel "Elevating" the old system which we cannot afford have it suffer "significant functionality failures".

    1
  • brandon45

    has anyone actually tried to do a do-release-upgrade on a cpanel server? from my understanding cpanel elevate was created because there isn't really a way to upgrade centos7 to alma 8 or others rhel 8 clones but with ubuntu upgrading between major releases is pretty straightforward with do-release-upgrade

    I think that the only thing that would need to be done manually is change the mirrors urls in sources.list.d to match 22.04/jammy

    0
  • vander.host

    brandon45

    I think it's worth a shot, but carefully also consider cPanel's staff comment:

    cPanel doesn't yet support in-place upgrades on Ubuntu, so the *official* answer would be to use the Transfer Tool to migrate to a newer machine

    If you risk this, and you break something, there officially you wouldn't get support or you'll have trouble. For test systems, this is okay, but on my live servers, this is just looking for trouble.

    I think the most productive way to tackle this issue is to post results of such an upgrade or comment on this wonderful roadmap site which I only recently discovered:

    ELevate Ubuntu 20.04 to 22.04
    https://features.cpanel.net/tabs/11-planned-roadmap

    In my experience, in place upgrades can be magic and sometimes a complete nightmare.

    0
  • cPRex Jurassic Moderator

    Someone else just asked me about that feature as well, and I've been told by the team that work will be more focused on that feature in Q3 of this year.

    1
  • pclp19

    any solution for this issue?

    0
  • cPRex Jurassic Moderator

    pclp19 - if you need to upgrade at this time, a traditional migration is the best way to do so.

    0
  • eitanc

    cPRex, "at this time" is not clear. We need definitive answers, to know where we are standing, so we can plan and not be left in the dark:

    1. Does cPanel have a plan to allow current 118.* installations to upgrade, in-place, on the current server, from Ubuntu 20 to 24 and then to cPanel 120.*?

    2. If there is a plan, what is the time line?

    3. If there is no such plan, and the only way to ever upgrade from 118 is to create and new server, with Ubuntu 24, and do a cPanel migration process - let us know this explicitly.

    0
  • cPRex Jurassic Moderator

    Well, I can't predict the future, so "at this time" is the best I have.  There could be a vastly increased need for this in the near future that changes the development path.

    So, for now, let's just say "no"

    0
  • eitanc

    I am not asking anyone to predict the future.

    A decent software company has a public road map for its products and services.

    Any lack of reference to this issue means one thing - the current situation will never change.

    CP is practically chasing its customers away, and it is a shame.

    0
  • cPRex Jurassic Moderator

    If it's not on the roadmap at https://features.cpanel.net/tabs/11-planned-roadmap it's not planned in the near future.

    0
  • siace

    Hi,

     

    First of all I'd like to ask cPRex, what happend to my old account 'uadm' that been login to the forums for years and years and now I have to login with cpanelID?

     

    Anywhy...

     

    I was running ubuntu 20.04 and had the same problem. This are the steps I did to upgrade to latest cpanel release:

     

    (upgrade of ubuntu is pretty simple and not needing any support from cpanel, however read on)

    # do-release-upgrade

    # reboot

     

    (following two commands are used, as package base-files was not updated due to unmet deps, which I think is a bug in the update process)

    # wget http://mirrors.kernel.org/ubuntu/pool/main/b/base-files/base-files_12ubuntu4_amd64.deb

    # dpkg -i base-files_12ubuntu4_amd64.deb

     

    (following line just to be clear)

    # apt update;apt upgrade;reboot

     

    (done ubuntu update, clear for upcp)

    # /scripts/upcp

     

    (all done).

     

     

    Good luck.

    1
  • cPRex Jurassic Moderator

    siace - we updated our Forums software in December, and it is now linked with the same user ID and password that we use for our support ticket system.

    0
  • eitanc

    cPRex, does what siace offered is supported by CP? counted as legit by CP?

    0
  • cPRex Jurassic Moderator

    OS upgrades like that are not something cPanel officially supports.  I'm glad it worked, but try it at your own risk.

    0
  • eitanc

    Thanks cPRex, so, just for my understanding, future-wise - CP as a policy, doesn't support customers upgrading main branches versions of CP supported distributions, in place, but instead asking customers to install the new branch version on a new server, install there a fresh CP and then do a migration? This is the rule?

    0
  • cPRex Jurassic Moderator

    If the OS isn't yet supported by ELevate, yes, that is correct.  That's just a traditional migration with the Transfer Tool.

    0
  • eitanc

    Thanks cPRex, so since ELevate, https://cpanel.github.io/elevate/, is currently not supporting Ubuntu at all, there is currently no way to use it at any Ubuntu, regardless of its version source and target, right?

    So for the visible future - CP supported Ubuntu major version upgrades will always needed be done using CP migration, right?

    But non-major Ubuntu upgrades can be done in-place, right?

    0
  • cPRex Jurassic Moderator

    That's correct.

    0
  • eitanc

    Thank you cPRex.

    I don't recall that this info was shared at any relevant CP documentation published regarding the move from CentOS to Ubuntu. I may have selected another distribution to move to.

    If I missed it - my problem, but if not - it will be kind of CP to publish this publicly in a prominent way at a relevant CP documentation content, to let customers be aware of this issue and decide based on this info.

    0

Please sign in to leave a comment.