To upgrade your cPanel and WHM software to the latest version, navigate to WHM's Upgrade to Latest Version interface (WHM >> Home >> cPanel >> Upgrade to Latest Version) and click the upgrade button. The system will automatically update to the most recent build available on your server's selected release tier, ensuring you have the latest features, security patches, and improvements.
Keeping your server software up to date is essential for maintaining security, stability, and access to new features. OBHost makes this process straightforward through the WHM interface, though you can also perform updates via command line if preferred.
Understanding Release Tiers and Versions
Before upgrading, it's important to understand that cPanel and WHM use different release tiers to manage updates. Your server is configured to follow a specific tier (such as CURRENT, RELEASE, STABLE, or LTS) through the Update Preferences interface in WHM. When you upgrade, the system will install the latest version available within your chosen tier, not necessarily the absolute latest version across all tiers.
You can check your current cPanel and WHM version by looking at the top right corner of the WHM interface. Alternatively, run the command /usr/local/cpanel/cpanel -V from the command line to view version information. To see what the latest available version is for your release tier, visit the official cPanel httpupdate page.
How to Upgrade Through WHM
The upgrade process through WHM is designed to be simple and user-friendly. Follow these steps to update your software:
- Log into WHM as the root user
- Navigate to Home >> cPanel >> Upgrade to Latest Version
- Review the current version information displayed on the page
- If you want to force a complete reinstallation of all files (useful if you suspect file corruption), select the checkbox to force reinstallation
- Click the Click to Upgrade button to begin the update process
The upgrade process will display real-time output showing its progress. Depending on your server's specifications and internet connection, the upgrade may take anywhere from a few minutes to over an hour. Do not close the browser window or interrupt the process while it's running.
Upgrading via Command Line
For those who prefer working from the command line or need to automate the upgrade process, you can run the update script directly. Log into your server via SSH as the root user and execute:
/scripts/upcp
This script is the same one that runs when you click the upgrade button in WHM. It will perform a full system update, including cPanel core files and many related software components. You can add the --force flag to force a reinstallation even if the system believes it's already up to date.
What Gets Updated During the Upgrade
When you run the upgrade process, you're not just updating cPanel and WHM themselves. The main upgrade script calls numerous other update scripts that refresh many components of your hosting environment:
- Core cPanel and WHM files: The primary control panel software and all its modules
- System RPMs: Various system-level packages maintained by cPanel
- Apache and web server components: Including EasyApache profiles if configured
- PHP versions: Updates to installed PHP versions
- Mail server components: Including Exim and related mail system files
- Database software: MySQL or MariaDB updates where applicable
- Security components: Including cPHulk, CSF configurations, and other security tools
- Additional services: FTP servers, DNS software, and various utilities
This comprehensive update approach ensures your entire hosting environment stays current and secure, not just the control panel interface.
Understanding Upgrade Blockers
Sometimes the upgrade process will stop and display warning messages about upgrade blockers. These are conditions that prevent the upgrade from completing safely. Common upgrade blockers include:
- Unsupported operating system versions that are too old
- Insufficient disk space to complete the upgrade
- Modified core files that would be overwritten
- Incompatible third-party plugins or customizations
- Database issues that need resolution first
If you encounter an upgrade blocker, carefully read the warning message. It will typically explain what the issue is and provide guidance on how to resolve it. You must address the blocker before the upgrade can proceed. In some cases, this might mean freeing up disk space, backing up customizations, or updating your operating system first.
Automatic Updates and Maintenance
In addition to manual upgrades, cPanel and WHM can be configured to apply updates automatically. You control this behavior through the Update Preferences interface in WHM (Home >> Server Configuration >> Update Preferences). Here you can:
- Choose your preferred release tier
- Enable or disable automatic updates
- Schedule when automatic updates should run
- Configure notification settings for update completion
- Set staging options for testing updates before production
If automatic updates are disabled on your server and you want to re-enable them, you'll see an option to do so in the Upgrade to Latest Version interface. Many server administrators prefer automatic updates for security patches while manually controlling major version upgrades.
Best Practices for Upgrading
To ensure smooth upgrades with minimal disruption, follow these recommended practices:
Create backups before upgrading: Always ensure you have current backups of your server configuration, account data, and any customizations before starting an upgrade. While upgrades are generally safe, having backups provides insurance against unexpected issues.
Schedule during low-traffic periods: Plan upgrades for times when your websites receive the least traffic, typically early morning hours. This minimizes the impact if the upgrade takes longer than expected or requires troubleshooting.
Review release notes: Before upgrading, check the cPanel release notes for your target version. These documents highlight new features, deprecated functionality, and any known issues you should be aware of.
Test in staging first: If you have a staging server, test the upgrade there before applying it to production. This helps identify any compatibility issues with your specific configuration or installed applications.
Monitor the upgrade process: Don't start an upgrade and walk away. Watch the output for errors or warnings that might require attention. If you're upgrading via command line, consider using screen or tmux to prevent disconnection issues.
Troubleshooting Common Upgrade Issues
If you experience problems during or after an upgrade, here are some common issues and solutions:
Upgrade appears stuck: If the upgrade seems to hang with no output for an extended period, it may actually still be working. Large updates can have long quiet periods. Wait at least 30 minutes before considering intervention. If you must investigate, check system resource usage and network connectivity.
Services not starting after upgrade: Occasionally services like Apache or MySQL may not restart properly after an upgrade. Try manually restarting them through WHM's Restart Services interface or via command line using the appropriate service commands.
Broken functionality after upgrade: If specific features stop working after an upgrade, check the error logs in WHM. Often this indicates a configuration incompatibility or a third-party plugin that needs updating.
Rollback needs: While cPanel doesn't provide a built-in rollback mechanism, you can restore from backups if you experience critical issues. This is why pre-upgrade backups are essential.
How often should I upgrade cPanel and WHM?
The upgrade frequency depends on your release tier configuration. If automatic updates are enabled, security patches and minor updates install as soon as they're available. For manual upgrades, check for updates at least monthly to ensure you have the latest security fixes. Major version upgrades can be performed quarterly or when specific new features are needed.
Will upgrading cause website downtime?
Most cPanel and WHM upgrades complete with minimal or no downtime for hosted websites. Services may restart briefly during the upgrade, causing a few seconds of interruption. However, the upgrade process itself can take 30-60 minutes during which you shouldn't make server configuration changes. Plan accordingly and inform clients if you manage multiple accounts.
Can I upgrade from very old versions directly to the latest?
Yes, cPanel's upgrade process handles multi-version jumps automatically. If you're running a very outdated version, the system will apply all intermediate updates in sequence to reach the latest version in your release tier. However, very old versions may encounter upgrade blockers that require addressing first, such as operating system compatibility issues.
What should I do if the upgrade fails?
If an upgrade fails, first review the error messages displayed or check the upgrade logs located in /var/cpanel/updatelogs/. The error messages usually indicate what went wrong. Common solutions include freeing disk space, fixing file permissions, or resolving package conflicts. If you cannot resolve the issue, restore from your pre-upgrade backup and contact your hosting provider's support team for assistance.
For additional help with upgrading your cPanel and WHM software or troubleshooting any issues you encounter, the OBHost support team is available 24/7. Visit https://www.obhost.net/contact or email support@obhost.org for expert assistance with your server management needs.
