~2 min read • Updated Feb 17, 2026
1. Introduction
The rpm.versions system in cPanel & WHM controls whether specific RPM or DEB packages are installed, updated, or removed. If you do not want the system to manage a package, you can set its target to unmanaged. This guide explains how to set or unset package management for any target.
Note: Before version 98, this feature was called “RPM Management.” Starting with version 98, DEB packages were added for Ubuntu installations.
2. Common Problems with Unmanaged Packages
Warning: It is strongly recommended to keep all targets managed by the rpm.versions system.
- Unmanaged packages do not receive automatic updates.
- Unmanaged FTP targets may break FTP-related interfaces in cPanel.
- Unmanaged targets may block future cPanel & WHM upgrades.
3. Why Is My Target Unmanaged?
Some targets may appear unmanaged even if you did not modify them:
- FTP —
proftpdandpure-ftpd - NSD —
nsd(removed in version 106; target removed in version 112)
4. What Is an rpm.versions Target?
The file /usr/local/cpanel/etc/rpm.versions contains target_settings, which define whether each target is managed or unmanaged.
Example: The clamav target controls the following packages:
cpanel-clamavcpanel-clamav-virusdefscpanel-perl-123-file-scan-clamav
5. List of Available Targets
| Service | Target | Warning |
|---|---|---|
| Third-party software | 3rdparty | Never set to unmanaged |
| Analog Stats | analog | |
| AWStats | awstats | |
| ClamAV | clamav | |
| Composer | composer | Removed in version 130 |
| cPanel | cpanel | Never unmanaged |
| Developer Tools | cpanel-devel | |
| Privilege Management | cpanel-wrap | Never unmanaged |
| Exim | exim | Advanced users only |
| FTP | proftpd / pure-ftpd | |
| Git | git | |
| Mailman | mailman | |
| Munin | munin | |
| MyDNS | mydns | Removed in version 112 |
| NSD | nsd | Removed in version 112 |
| Obsolete services | obsolete | |
| p0f | p0f | |
| phpMyAdmin | phpmy | |
| PAM | pam | |
| Perl 5.32 | perl532 | Never unmanaged |
| Perl 5.36 | perl536 | Never unmanaged |
| Perl 5.42 | perl542 | Never unmanaged |
| PHP | cpanel-php81 / php83 / php84 | |
| PowerDNS | powerdns | |
| Roundcube | roundcube | |
| Site Publisher | sitepublisher | Removed in version 134 |
| SQLite | sqlite | |
| User Interface | userinterface | |
| Webalizer | webalizer |
6. Set a Target to Unmanaged
Use the following command, replacing service with the target name:
/usr/local/cpanel/scripts/update_local_rpm_versions --edit target_settings.service unmanagedFor FTP, run the command twice:
pure-ftpdproftpd
6.1 Confirm the Target Is Unmanaged
Open:
/var/cpanel/rpm.versions.d/local.versionsExample:
target_settings:
cpanel-devel: installed
roundcube: unmanaged7. Return a Target to Managed
To restore the default managed state:
/usr/local/cpanel/scripts/update_local_rpm_versions --del target_settings.serviceFor FTP, run the command for both targets.
7.1 Confirm the Target Is Managed
The target should no longer appear in target_settings.
Conclusion
The rpm.versions system is essential for maintaining package stability and compatibility in cPanel & WHM. While you can set targets to unmanaged, doing so should be approached with caution due to potential service issues and upgrade blockers. This guide provides the necessary steps to safely manage or unmanage package targets.
Written & researched by Dr. Shahin Siami