Plan Webuzo panel, managed-application and operating-system updates as related maintenance tasks with separate compatibility checks. Keeping one component current does not prove the others have received their security fixes.
IN THIS ARTICLE
Prepare for the change
Record installed versions, available updates, custom configuration and recent backups. Confirm that you can recover the server and applications. Review release notes and schedule disruptive changes when you can observe the result rather than immediately before leaving the system unattended.
01 Update Webuzo and its software stack safely
- Open the Webuzo Update page and compare the installed and offered panel versions. Use the supported update action for an approved stable release.
- Inspect Settings > Update Settings and document the selected automatic-update channel and notifications. A release-candidate channel is a testing choice and should not be enabled casually on production.
- Review Apps > Update Apps separately. Inspect each application auto-upgrade policy, distinguishing minor-only updates from major-version changes and manually managed updates.
- Test runtime and database major upgrades in an equivalent environment first. A backup must include a realistic restore method because database downgrade is not a generic one-click operation.
- Review Updates > System Update for operating-system packages and whether kernel packages are included. Plan any required service restart or reboot and retain console access.
- Apply the approved updates, inspect completion logs and verify running versions. Avoid starting overlapping package or application update jobs.
Should every available major update be automatic?
Only when the applications and recovery process are prepared for that policy. A supported security-maintenance update and a major runtime change can have very different compatibility effects.
Confirm the expected result
Test panel login, representative websites, database writes, mail and scheduled tasks. Confirm the running kernel after a planned reboot when a kernel update was applied. Monitor errors and ensure backup jobs continue under the updated environment.
If the change does not work
If an update fails, preserve the first error and determine which component is incomplete. Do not rerun all upgrades blindly or disable signature and TLS checks. Restore or repair through the component supported procedure, keeping application data created after the backup in mind.