Update Preferences defines the cPanel release tier and update behaviour. Choose a supported policy that balances timely fixes with your testing and maintenance process rather than indefinitely freezing an old build.
IN THIS ARTICLE
Information to have ready
Record the current version, release tier, operating-system support and critical integrations. Keep verified backups and review relevant release notes before a significant version transition.
01 Choose a cPanel update policy and maintenance window
- Open Update Preferences and review the available supported release tiers and their intended stability or support characteristics.
- Select a tier appropriate to the production service and review automatic or manual update settings. A manual policy needs a named operator and reliable schedule.
- Review operating-system package and maintenance settings separately. Do not assume the cPanel application tier controls every server package.
- Coordinate the maintenance run time with backup, transfer and peak-traffic schedules using the server’s supported scheduling controls. Save the intended policy.
- Observe the next update, review completion logs and test panel access, websites, mail and critical integrations. Address failures promptly rather than disabling all updates.
Confirm the expected result
The server should follow the documented update policy and remain on a supported release with successful maintenance runs. Keep alerts for update failures and approaching end of support.
Troubleshoot unexpected results
If an update is blocked, inspect the stated operating-system, package or compatibility prerequisite. Do not force a custom version pin without understanding its support consequences. A release-tier change is not a guaranteed downgrade mechanism.
Is the oldest available tier always safest?
No. Stability also requires ongoing security support. Select a supported tier that fits your change process and plan migration before its support window ends.