A HostBill installation needs a compatible runtime, a valid licence and the particular integration modules used by your business. Check these before purchasing server capacity or moving customer records. A working PHP website alone does not establish that billing automation will work.
IN THIS ARTICLE
01 Build an installation checklist
- Choose the deployment method. Decide between manual installation in an existing hosting environment and the vendor installer supplied with your purchase. An installer that configures a web server and database belongs on a suitable fresh system. Check the current instructions attached to your licence.
- Check the release requirements. Compare the target HostBill build with the official requirements. These include Linux, a supported PHP environment, compatible database configuration, ionCube Loader and the required PHP extensions. Record the actual versions instead of relying on a hosting plan's marketing description.
- Check both PHP environments. The website and command-line cron may use different PHP binaries. Confirm that both load the required extensions and that the automation account can read the application files.
- List your integrations. Record the provisioning applications, registrars, gateways, authentication tools and order pages you intend to use. Confirm availability in your purchase and compatibility with the target version.
- Prepare the operating details. Reserve an HTTPS billing address, database credentials, transactional sender, backup destination and staff recovery method. Decide who owns cron monitoring and release updates.
02 Verify before proceeding
Ask the server administrator to confirm resource limits and outbound connectivity to your chosen providers. Ensure backups can be restored without depending on the same failed server. Record a simple go-live test: one customer, one invoice, one payment test and one controlled provisioning request.
03 Example: check the PHP used by cron
Ask the administrator to run these read-only checks as the account that will run HostBill automation. Replace /usr/bin/php with the exact binary specified in the intended cron command.
/usr/bin/php -v
/usr/bin/php --ini
/usr/bin/php -mRecord the PHP version, loaded configuration paths and extension list, then compare them with the requirements for the installed HostBill release. These commands describe command-line PHP only. Compare their results with the web application's runtime information as a separate step. If the website uses a supported PHP version but cron loads another version or lacks ionCube, correct the cron runtime before activating scheduled billing.
Common questions
Does a HostBill licence include every integration?
Do not assume so. Match each required application or plugin with the modules available in your licence and purchase records. A public integration guide demonstrates a supported workflow, not entitlement to that module.
Can I use an automatic installer on my existing production server?
Only if the supplied installer instructions explicitly support that arrangement. An installer that replaces or configures system services can affect other websites. A separate compatible system gives you a clearer installation and recovery boundary.