How to fix the cPanel ELevation blocker issue detected on CentOS 7? Let’s see the troubleshooting. At Bobcares, with our cPanel & WHM Support Services, we can handle your cPanel ELevate issues.

How to Fix the cPanel ELevation Blocker Issue Detected on CentOS 7?

There are several possible causes for the elevation blocker problem, including, sudo setup variations between AlmaLinux and CentOS 7, Certain actions during the migration process being blocked by SELinux policies, Permission issues or incorrect setup affecting the running of commands with elevated privileges, and package dependencies or the migration script are having problems.

When we run this script, we must make sure the following criteria exist:

• We are running CentOS 7.9 or later.

• We are running cPanel version 102 or later.

• Log in as the root user.

By getting elevate-cpanel and running /scripts/elevate-cpanel –check, we can find a lot of these problems. Also, an overview of the main challenges people may run into is provided below.

1. Firstly, we must be on a version mentioned in the “Latest cPanel & WHM Builds.

2. cPanel supports a large number of nameservers. (bind, powerdns, nsd, MyDNS). So, it is advisable to always use PowerDNS on AlmaLinux 8 / Rocky 8.

3. MySQL 8 is set up on 99% of current AlmaLinux 8 / Rocky 8 cPanel setups. So, update the MySQL to version 8.0.

4. AlmaLinux 8 / Rocky 8 didn’t support some EA4 packages.

5. It must be possible for the system to modify the GRUB2 setup in order to control the boot process.

6. The machine has multiple NICs using kernel names (ethX).

Troubleshooting cPanel ELevation Blocker Issue

If a cPanel elevation blocker error occurs, we can try the following steps:

• Run /scripts/elevate-cpanel –check after downloading elevate-cpanel.
• Look for blockers.
• Reboot after updating yum.
• Delete any installed software that comes with a cPanel system.
• AlmaLinux upgrade.
• Any software that was removed before the upgrade should be reinstalled.
• Turn off any enabled, unsupported YUM repos with installed packages.
• Unsupported YUM repositories’ installed packages should be removed.
• Begin a fresh run using  /scripts/elevate-cpanel –clean. To double-check everything, clean everything.
• On the system, the /sbin/grubby file should have root:root ownership and 755 permissions.

[Searching solution for a different question? We’re happy to help.]

Conclusion

The article offers a brief note from our Tech team on fixing the cPanel ELevation blocker issue detected on CentOS 7.