App Installers and panel modules
Manage Softaculous connectivity and install trusted BigCloudy panel modules.
1Overview
App Installers combines the default application installer configuration with the panel module installer. Uploaded modules are disabled first and can run privileged backend code only after an administrator enables them.
2Before you begin
Administrator actions can affect multiple customer accounts and server services.
3Step-by-step workflow
Open App Installers, use the module ZIP control for a package in the documented BigCloudy format, review its module name, version, and checksum, then enable it only when its author and contents are trusted. Use Open module to configure an enabled module.
- Open App Installers and identify whether you are configuring Softaculous or managing a BigCloudy panel module.
- For Softaculous, review the selected installer and the connection settings requested by the page.
- Test the connection and save only the settings intended for this server.
- For a module, obtain its ZIP from a trusted developer and review its contents before uploading.
- Use the Module ZIP field and Upload module, then inspect the displayed name, version, status, and checksum.
- Leave the module disabled until it has been reviewed; uploaded code is not automatically trustworthy.
- Enable the approved module and use Open module to view its settings.
- Keep the source package and a configuration backup so the module can be disabled or rolled back if it causes a problem.
4Practical example
Example: a panel integration module extends the hosting control panel. Installing that module is different from installing WordPress inside a customer website through the application installer.
5Verify the result
Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.
- Refresh modules and confirm the expected enabled state.
- Open the module once and confirm it loads without a panel error.
6Common problems and what to check
The ZIP is rejected: check the documented package structure and upload limit shown beside the field.
Open module fails: inspect its status, version compatibility, and the relevant panel log.
Softaculous is unavailable: confirm the connection and licence with the provider; reinstalling a customer website will not repair that connection.
7Security, impact, and rollback
Treat a module ZIP like server software. Keep a copy of the source package, check its checksum, and never enable unreviewed code because enabled modules run with panel-service privileges.