Things to check before running cPanel ELevate on an inherited CentOS 7 VPS?
Hello everyone,
I currently have a VPS with the following setup:
- OS: CentOS v7.9.2009 STANDARD kvm
- cPanel Version: 110.0.112
I know that cPanel & WHM version 110 is the last version supporting CentOS 7, so I’m considering using cPanel ELevate to migrate to AlmaLinux 8.
My main concern is that I did not originally build or configure this VPS. I inherited it from another administrator, so I do not fully know everything that may be customized internally.
So far, I’ve mostly handled basic administration tasks such as:
- Firewall management
- WP Toolkit
- Checking/fixing mail errors
- Mail relay configuration
- General basic maintenance
But beyond that, I have not deeply modified or audited the server configuration.
Before running `cpanel elevate`, I would like to ask:
- What should I absolutely verify before starting the upgrade?
- Are there common legacy configurations that usually cause issues during ELevate?
- How risky is it to run ELevate on a server with an unknown admin history?
- Would you strongly recommend taking a full VPS snapshot/backup beforehand?
- Have you experienced issues with mail services, Apache/Nginx, MySQL, or custom configurations after upgrading?
Any advice, best practices, or pre-check recommendations would be greatly appreciated.
-
Hey there! cPanel ELevate includes the "--check" option, which will check the system for you before you attempt to run ELevate. You can find details on this here:
https://cpanel.github.io/elevate/blockers/
I'll go through and answer the rest of those questions in order to ensure I don't miss anything:
Q1 - What should I absolutely verify before starting the upgrade?
A1 - The --check script will confirm any blockers on the system, and you'll want to resolve all those before you run ELevateQ2 - Are there common legacy configurations that usually cause issues during ELevate?
A2 - If there are, --check will find them. If you know that you're using old MySQL or PHP versions, you'll want to plan ahead and how you'll handle those sites.Q3 - How risky is it to run ELevate on a server with an unknown admin history?
A3 - I wouldn't say this is risky at all. A vast majority of servers have been running for years, and it's unlikely detailed notes have been kept about everything that has happened to them in that time.Q4 - Would you strongly recommend taking a full VPS snapshot/backup beforehand?
A4 - I would do both, if possible.Q5 - Have you experienced issues with mail services, Apache/Nginx, MySQL, or custom configurations after upgrading?
A5 - I'm sure some users have, but I don't have any widespread reports saying "this specific thing is going to break." ELevate has been out for some time now and is generally very stable.0
Please sign in to leave a comment.
Comments
1 comment