If your dedicated server runs cPanel & WHM on Rocky Linux, you need to plan an operating system migration before upgrading to cPanel version 134 or later.
Starting with cPanel & WHM version 134, Rocky Linux 8 and Rocky Linux 9 are no longer supported. This means existing Rocky Linux servers cannot continue upgrading to newer cPanel versions while remaining on Rocky Linux.
AlmaLinux is the recommended replacement because it provides a compatible RHEL-based environment for cPanel hosting.
The good news is that you do not necessarily need to build a completely new server and manually move every website. You can convert an existing Rocky Linux installation to AlmaLinux using the official AlmaLinux migration script recommended by cPanel.
Quick Answer: To migrate a cPanel server from Rocky Linux to AlmaLinux, first create a complete off-server backup, check your existing server configuration and obtain reliable console access. Update the operating system packages, download the official almalinux-deploy.sh script and run it as root. Once the conversion completes, reboot the server and verify that AlmaLinux is running correctly. After checking cPanel services, accounts and websites, you can proceed with a supported cPanel version 134 upgrade.
This guide explains how to convert Rocky Linux 8 to AlmaLinux 8 and Rocky Linux 9 to AlmaLinux 9 while retaining your existing cPanel hosting environment.
Why Do You Need to Migrate from Rocky Linux to AlmaLinux?
The main reason for this migration is a change in cPanel's operating system support policy.
cPanel announced that Rocky Linux 8 and Rocky Linux 9 support would end with cPanel & WHM version 134, released in 2026.
From version 134 onwards:
New cPanel installations on Rocky Linux are blocked.
Existing Rocky Linux servers cannot upgrade to cPanel v134 or later.
AlmaLinux is recommended as an alternative.
Existing hosting environments need an operating system migration to remain compatible with newer cPanel releases.
This change affects hosting providers, web agencies, resellers and businesses operating cPanel servers on Rocky Linux.
For example, if your dedicated server currently runs Rocky Linux 9 with cPanel & WHM, you should convert the operating system to AlmaLinux 9 before attempting to upgrade cPanel to version 134.
Rocky Linux vs AlmaLinux: What Changes During Migration?
Rocky Linux and AlmaLinux are both enterprise Linux distributions based on Red Hat Enterprise Linux (RHEL) sources.
They provide similar server environments, including package management through DNF, system administration through systemd and support for common Linux hosting applications.
However, cPanel's operating system support policy now makes AlmaLinux the appropriate choice for new and upgraded cPanel environments.
The following comparison explains the main differences relevant to this migration.
| Feature | Rocky Linux | AlmaLinux |
|---|---|---|
| Linux distribution | RHEL-compatible | RHEL-compatible |
| Package manager | DNF | DNF |
| System management | systemd | systemd |
| cPanel v134 support | Not supported | Supported |
| Existing cPanel hosting | Requires OS migration | Supported |
| Recommended for new cPanel servers | No | Yes |
The migration changes the underlying operating system packages, release information, repositories and system identification.
It is not simply a change to the operating system name. The conversion process replaces Rocky Linux distribution components with their AlmaLinux equivalents.
Your existing cPanel accounts and hosting data can remain on the server, but you must verify the environment after conversion.
Can You Migrate Rocky Linux 8 and 9 Directly to AlmaLinux?
Yes. The AlmaLinux migration tool supports converting both Rocky Linux 8 and Rocky Linux 9 to their corresponding AlmaLinux versions.
The recommended migration paths are:
Rocky Linux 8 → AlmaLinux 8
Rocky Linux 9 → AlmaLinux 9
The conversion script changes the distribution while keeping the same major operating system version.
For example, if your server runs Rocky Linux 9, the migration converts it to AlmaLinux 9. It does not automatically upgrade the server to AlmaLinux 10.
Important: Do not combine an operating system conversion with a major-version upgrade unless you have separately planned and verified that upgrade. Keeping the same major version reduces the number of changes made during the migration.
Requirements Before Migrating Your cPanel Server
An operating system conversion affects important system components. Before running the migration script, make sure your server meets the following requirements.
1. Root SSH Access
You need root-level access to the Rocky Linux server.
Connect through SSH:
ssh root@YOUR_SERVER_IP
Replace YOUR_SERVER_IP with your server's public IP address. You can also use WHM's Terminal interface if SSH access is unavailable, provided you have the required root permissions.
2. A Complete Server Backup
Backups are essential before changing the operating system.
Create:
Full cPanel account backups.
Database backups.
Website and application file backups.
Email backups.
Custom configuration backups.
A complete server image or provider-level snapshot.
Store backups outside the server being migrated.
WHM account backups protect cPanel-managed account data, but they are not a replacement for a complete system image. Custom services, system-level configurations and applications outside cPanel may not be included. If your hosting provider supports remote snapshots, create one before proceeding.
3. Sufficient Disk Space
The migration process downloads and installs replacement operating system packages.
Check available disk space:
df -h
Check inode availability:
df -ih
Pay particular attention to /, /boot, /var and the filesystems used by your cPanel accounts.
The AlmaLinux migration documentation recommends checking that /boot has enough available space. A 512 MB boot partition is generally sufficient for three kernel versions, although your actual requirements depend on the installed kernels and configuration.
4. Reliable Console Access
An operating system migration may involve changes to the kernel, bootloader and system packages.
If the server fails to boot or loses network connectivity, you need another way to access it. Keep at least one alternative access method available:
KVM over IP.
Provider rescue console.
Do not rely entirely on your active SSH session.
5. Check Your Current cPanel Version
Before migration, identify the installed cPanel version:
/usr/local/cpanel/cpanel -V
Also check the operating system:
cat /etc/os-release
Record the current version, operating system and server hostname.
Step 1: Check the Current Rocky Linux Installation
Before making changes, collect information about your existing server.
cat /etc/redhat-release
uname -r
/usr/local/cpanel/cpanel -V
free -h
df -h
systemctl --failed
Record the output so you can compare the system before and after migration.
You should also review any custom repositories, third-party RPM packages, additional PHP modules, firewall configurations and external services running on the server. These components may require additional attention after the operating system conversion.
Step 2: Back Up cPanel Accounts and Server Configurations
Create cPanel Account Backups
Log in to WHM as root.
Navigate to: WHM → Backup → Backup Configuration
Enable account backups and select a suitable backup destination.
For additional protection, you can create manual account backups through the command line:
/usr/local/cpanel/scripts/pkgacct USERNAME
Replace USERNAME with the actual cPanel account username.
Back Up Important System Configurations
cPanel account backups do not include every system-level configuration. Depending on your server setup, preserve copies of:
Custom Apache configuration.
DNS configuration.
Firewall rules.
Custom systemd services.
Important: Do not continue unless you have verified that your backups are accessible and can be restored. A successful backup job does not automatically mean that the backup is usable.
Step 3: Update Rocky Linux Packages
Before converting the operating system, update the existing Rocky Linux packages.
dnf update -y
If the update installs a new kernel or requires a restart, reboot the server:
reboot
Reconnect after the server becomes available. Check the system again:
cat /etc/redhat-release
Confirm that the server is still running the expected Rocky Linux major version.
Important: Do not attempt to force a cPanel v134 upgrade while the server is still running Rocky Linux. Complete the operating system conversion first.
Step 4: Download the AlmaLinux Migration Script
The AlmaLinux migration tool, almalinux-deploy.sh, converts supported RHEL-compatible distributions to AlmaLinux. cPanel specifically recommends this script for migrating existing Rocky Linux servers.
curl -O https://raw.githubusercontent.com/AlmaLinux/almalinux-deploy/master/almalinux-deploy.sh
You can check that the file exists:
ls -lh almalinux-deploy.sh
The script must be obtained from the official AlmaLinux project repository. Avoid downloading operating system migration scripts from unknown third-party websites.
Step 5: Convert Rocky Linux to AlmaLinux
Once your backups are ready and the script has been downloaded, you can start the conversion.
bash almalinux-deploy.sh
The migration tool will begin replacing Rocky Linux distribution packages with their AlmaLinux equivalents. During this process, the script performs tasks such as checking the existing operating system, configuring AlmaLinux repositories, and installing the appropriate AlmaLinux kernel.
Important: Allow the script to complete without interrupting it. Do not close the console, restart the server manually or terminate the running process while the conversion is in progress.
Check the Migration Output
After the conversion finishes, review the output for errors. A successful conversion should display a completion message similar to:
Migration to AlmaLinux is completed
Do not treat this message alone as proof that every service is working. You still need to reboot and perform post-migration checks.
Step 6: Reboot the Server into AlmaLinux
reboot
The server should boot using the AlmaLinux kernel. Depending on your hardware, storage configuration and package updates, the reboot may take longer than usual. Use your IPMI, BMC or provider console to monitor the boot process if SSH does not become available.
Once the server is online, reconnect:
ssh root@YOUR_SERVER_IP
Check the operating system:
cat /etc/redhat-release
For a Rocky Linux 9 conversion, the output should identify AlmaLinux 9.
Step 7: Verify the AlmaLinux Migration
Do not immediately upgrade cPanel after rebooting. First, confirm that the operating system conversion was successful.
cat /etc/os-release
grubby --info DEFAULT | grep AlmaLinux
uname -r
dnf repolist
dnf check-update
systemctl --failed
Review any failed services before continuing. At this point, your operating system should be running AlmaLinux, but you still need to verify the cPanel hosting environment.
Step 8: Verify cPanel & WHM Services
Once AlmaLinux is running, check whether cPanel & WHM is still functioning correctly.
/usr/local/cpanel/cpanel -V
Access WHM through https://YOUR_SERVER_IP:2087 and log in as root.
Check the following:
Existing cPanel accounts and website accessibility.
Database connectivity and Email delivery.
DNS resolution and SSL certificates.
Apache or LiteSpeed services.
You should also check the cPanel error logs if any service fails to start.
tail -n 100 /usr/local/cpanel/logs/error_log
If a service is not working, investigate the error before proceeding with the cPanel upgrade.
Step 9: Upgrade cPanel & WHM to Version 134 or Later
Once the server is successfully running AlmaLinux and the hosting environment has been checked, you can proceed with the cPanel update.
You can check the current cPanel update configuration in: WHM → Server Configuration → Update Preferences. Choose an appropriate supported release tier.
You can then run the cPanel update process:
/usr/local/cpanel/scripts/upcp
Check the installed version afterwards:
/usr/local/cpanel/cpanel -V
Confirm that the server is running the intended supported cPanel version. Do not force an update if the operating system conversion or cPanel service checks have failed.
Step 10: Perform Post-Migration Security and Maintenance Checks
After upgrading cPanel, complete a final review of the server.
Review Firewall Rules: Check that your firewall configuration is still working. Operating system conversion may affect package-managed components and third-party firewall integrations.
Check SSL Certificates: Confirm that your hosted websites and cPanel services use valid SSL certificates.
Test Automated Backups: Run a backup test and confirm that files are being stored at the expected remote or external destination.
Monitor Server Resources: Use commands like
top,free -h, anddf -hto monitor CPU, memory, disk space and network activity after the migration.
Common Problems During Rocky Linux to AlmaLinux Migration
| Problem | Possible Cause | Recommended Action |
|---|---|---|
| Migration script stops | Package conflicts or repository errors | Review the script output and resolve the reported issue |
| Insufficient disk space | Not enough room for package downloads or kernel installation | Check filesystem usage and free the required space |
| Server fails to boot | Kernel or bootloader configuration issue | Use IPMI/KVM or rescue mode and investigate the boot configuration |
| SSH is unavailable after reboot | Network interface or firewall configuration issue | Use the remote console to inspect networking and firewall services |
| WHM does not load | cPanel service failure or firewall restrictions | Check cPanel logs and service status |
If the conversion fails, do not repeatedly run the migration script without understanding the error. Review the available logs and contact AlmaLinux or cPanel support when necessary. For servers containing important customer websites, restoring a verified server image may be safer than attempting an uncertain manual recovery.
Frequently Asked Questions
Why does cPanel no longer support Rocky Linux?
cPanel removed Rocky Linux 8 and 9 support starting with cPanel & WHM version 134. The change affects both new installations and upgrades. cPanel recommends AlmaLinux as an alternative for existing Rocky Linux hosting environments.
Can I migrate Rocky Linux 9 to AlmaLinux 9 without reinstalling the server?
Yes. The official AlmaLinux migration script supports in-place conversion from Rocky Linux 9 to AlmaLinux 9. However, a complete backup and reliable console access are essential before starting.
Can I convert Rocky Linux 8 to AlmaLinux 9 directly?
The standard AlmaLinux conversion script changes the distribution while retaining its major version. Therefore, Rocky Linux 8 converts to AlmaLinux 8, not directly to AlmaLinux 9. A major-version upgrade should be treated as a separate operation.
Will I lose my cPanel accounts during migration?
An in-place operating system conversion is designed to retain the existing server environment, including cPanel data. However, no migration is completely risk-free. Account backups and a complete server image should be created before conversion.
Do I need to reinstall cPanel after converting to AlmaLinux?
A successful in-place conversion does not normally require a fresh cPanel installation. The existing cPanel environment should be checked after the operating system conversion. You can then upgrade to a supported cPanel release.
Can I upgrade to cPanel v134 while running Rocky Linux?
No. cPanel v134 and later do not support Rocky Linux. You need to migrate to a supported operating system such as AlmaLinux before upgrading.
Is the AlmaLinux migration script safe for production servers?
The script is the migration method recommended by cPanel for this Rocky Linux transition. However, operating system conversions can still fail because of package conflicts, storage problems or custom configurations. Always test the process where possible and maintain an off-server recovery backup.
Does the migration change my server's IP address?
An in-place operating system conversion does not normally require changing the server's network IP address. However, always verify network configuration and connectivity after rebooting.
Conclusion
Migrating a cPanel server from Rocky Linux to AlmaLinux is an important step for hosting providers and administrators preparing for cPanel & WHM version 134 and later. By using the official AlmaLinux migration script, administrators can convert an existing Rocky Linux installation without automatically rebuilding the entire hosting environment.
If you are planning to run cPanel hosting workloads, choosing a reliable dedicated server with sufficient CPU, RAM, storage and network capacity is equally important.
Explore eServers UK's cPanel Dedicated Servers for dedicated hosting infrastructure designed for cPanel environments.
Discover eServers Dedicated Server Locations
eServers provides reliable dedicated servers across multiple global regions. Whether you need low latency, regional compliance, or proximity to your audience, our wide geographic coverage ensures the perfect hosting environment for your project.