How to Manage Installed Modules Print

Cockpit modules extend the base panel with additional app or feature support. The Admin page gives you the main place to review installed modules, compare local and remote versions, and decide what needs attention.

When to Use This

• You want to review which modules are currently installed.
• You need to check whether a module update is available.
• You are cleaning up a panel before handing it to a client.
• You want to understand the difference between installed and available modules.

What Module Management Helps You Do

• see what modules are already installed
• compare local versions against remote catalog versions
• identify modules that may need updating
• review module titles, icons, and general presence in the panel

Steps

1. Open the Admin page.
2. Find the module management area or installed modules list.
3. Review each installed module entry and compare the shown local version against any available remote version details.
4. Identify whether the module is current, outdated, or no longer needed.
5. Plan one module change at a time, especially on a live panel.

Expected Result

After reviewing the module list, you should know which modules are installed, which ones are current, and which ones need follow-up such as updating, testing, or removal.

Good Module Management Habits

• Keep only the modules you actively need.
• Review version differences before making changes.
• Do not combine module changes with a base panel update unless you have a good reason.
• Back up the panel before large module maintenance sessions.

Common Mistakes

• Updating everything at once: Large maintenance batches make it harder to isolate a problem if one appears.
• Ignoring version drift: Leaving older modules in place for too long can create confusion during troubleshooting.
• Assuming installed means enabled everywhere: Some module behavior may still depend on the module's own settings and configuration.
• Skipping backup before cleanup: If you remove or change the wrong thing, recovery is easier when a backup already exists.

Example Use Cases

• Client handoff: A reseller removes unused modules so the client sees a cleaner, less confusing panel.
• Routine review: The owner compares installed versions against the remote catalog and schedules follow-up maintenance.
• After a base update: The admin checks whether installed modules still look current and present correctly.

Related Articles

• Admin Page Tour
• How to Update Cockpit from the Admin Page
• How to Restore a Backup Safely
• How to Upload and Install New Panel Modules in Cockpit