Install the suite in the WHMCS installation that owns the services you want to manage. The package contains an addon, supporting module files and hooks, so uploading only the addon folder leaves some workflows unavailable.
IN THIS ARTICLE
01 Before uploading
Keep a current backup of your WHMCS database and files. Confirm that your WHMCS release, theme, gateways and other modules support the selected PHP version. Hosting Suite 1.0.40 targets 64-bit PHP 8.1, 8.2, 8.3 and 8.4, but its renewal invoicing adapter supports WHMCS 8 only. Check the requirements of the edition supplied with your purchase for any additional loading or licence steps.
You need permission to upload files and activate WHMCS addons. Database access must allow the module to create and update its own tables. Do not install the package in a separate public folder and try to open its PHP files directly.
02 Install the files and activate
- Extract the release archive locally.
- Upload its
modulesandincludescontents into the WHMCS root, preserving the directory structure. - Confirm that both
includes/hooks/nabtech_hosting_suite.phpandincludes/hooks/nabtech_hosting_suite_trials.phpare present. The trials hook also runs scheduled suite work when you do not offer trials. - In WHMCS, open System Settings > Addon Modules.
- Activate Nabtech Hosting Suite, choose Configure, select the administrator roles that may use it and save.
- Open Addons > Nabtech Hosting Suite. Review PHP & environment and the setup sections before enabling customer workflows.
03 Configure what customers receive
Activation creates the suite's storage. You still choose the enabled engines, hosting platforms, product features and renewal policies. Start with one representative service and confirm its account link. Leave the account-change switch off while reviewing lists; enable it when you are ready to test a controlled change.
Keep the normal WHMCS system cron configured. You do not need a second permanent worker cron for the suite. Scheduled renewals, trial checks and application follow-up work use the WHMCS cron integration.
How do I confirm that Hosting Suite installed correctly?
The addon should open for an authorised administrator. A configured test hosting product should show its permitted tools in Product Details, and the service domain should match the hosting account. Reopen the page after saving settings to confirm they persisted.
If activation fails, check the displayed PHP requirement, missing extensions, database CREATE/ALTER permissions and whether all files came from the same release. Do not repeatedly deactivate or select Delete all data on deactivate as a repair step. That option is a deliberate data-removal operation.
04 Plan the first maintenance window
Record the current addon configuration, product module assignments and cron command before installation. These details help distinguish a pre-existing server problem from a new integration issue. Have a test customer and an active sample hosting account ready so validation does not require experimenting with a customer's live website.
After activation, turn on one intended feature for one test product and inspect its full workflow. Adding a server module to the filesystem does not mean every existing product must be reassigned to it. Regular supported hosting products can retain their established provisioning module; dedicated application products use the suite's server-module workflow. Review this distinction before changing a product that already has customers and automated billing.