How to Update Cockpit from the Admin Page Print

The Admin page gives you the built-in workflow for updating the base panel. The safest way to use it is to check updater readiness first, confirm you have a current backup, and then run the update only when the panel reports that the environment is ready.

When to Use This

• A new base panel version is available.
• You want to update Cockpit without doing a manual file replacement.
• You want a repeatable update checklist for operators.
• You need to reduce the chance of update extraction failures.

Before You Start

• Make sure updater readiness is passing.
• Take or download a fresh backup before applying the update.
• Avoid running other major admin changes at the same time.
• If this is a production panel, choose a quiet maintenance window when possible.

Steps

1. Open the Admin page.
2. Review the updater area and confirm the readiness state is healthy.
3. Check whether a newer base version is available.
4. Create or download a backup before continuing.
5. Start the update from the Admin page.
6. Wait for the update process to finish fully. Do not interrupt the panel midway through extraction or replacement.
7. Reload the panel after completion and confirm the main pages still load normally.

Expected Result

After a successful update, Cockpit should load normally on the new version and the Admin page should no longer show that the same base update is pending.

Recommended Post-Update Checks

1. Log in again if the session refreshes.
2. Open Dashboard, Admin, Settings, and Downloads to confirm the main pages render cleanly.
3. Check that installed modules still appear correctly.
4. Revisit updater readiness to make sure the environment still reports healthy after the update.

Common Mistakes

• Skipping the readiness check: If the panel says the updater is blocked, fix that first.
• Updating without a backup: Recovery is slower and riskier when you do not have a recent backup package.
• Interrupting the update: Closing the tab or stopping the process too early can leave the installation in a mixed state.
• Ignoring hosting write limits: Shared hosting and locked-down VPS setups often need permission fixes before update extraction will work reliably.

Example Use Cases

• Routine maintenance: The owner applies the newest base update during a low-traffic window after verifying readiness and taking a backup.
• Post-support fix: Hosting support corrects write permissions, then the operator returns to Admin and reruns the update successfully.
• Pre-release polish: A reseller updates the panel before uploading new modules so the base platform is current first.

If the Update Fails

• Go back to updater readiness and identify the first failed check.
• Confirm the install path is writable by PHP for extraction.
• Confirm your server limits are high enough for the update package.
• If needed, restore from your backup and retry after fixing the environment.

Related Articles

• What Updater Readiness Means
• Admin Page Tour
• How to Restore a Backup Safely