Getting started with NodeWorx reseller hosting Print

  • 0

In short: NodeWorx is the reseller-level control panel. Create a reusable SiteWorx package first, then create each customer as a separate SiteWorx account. Keep the existing reseller identity and API key—never create a second reseller merely to troubleshoot an integration.

Understand the two account levels

  • NodeWorx: reseller administration, packages, SiteWorx accounts and service-wide settings.
  • SiteWorx: the individual customer's domains, files, databases, email, SSL and backups.

1. Create sensible packages

Open NodeWorx > SiteWorx > Packages and create packages that match the products you sell. Set storage, bandwidth, mailbox, database, cron, SSL and backup allowances deliberately. Use stable package names so billing-system mappings remain clear.

Good to know: Editing or deleting a package does not retroactively change existing SiteWorx accounts. Review existing accounts separately when changing a product's limits.

2. Create a SiteWorx account

  1. Open NodeWorx > SiteWorx > Accounts and choose Add a SiteWorx Account.
  2. Enter the master domain without www..
  3. Select the correct IP address, database server, package and PHP version.
  4. Set the account owner's contact email and a unique SiteWorx login.
  5. Review optional application-installer access and any custom resource limits before saving.

3. Connect automation carefully

If WHMCS will provision accounts, connect it to the existing reseller with a dedicated API key, map each WHMCS product to the correct InterWorx package, and test with a controlled order before enabling automatic provisioning.

Avoid duplicate or partial accounts: If an automated create action reports an error, check NodeWorx before retrying. The remote action may have completed even if the response was interrupted. Never delete an account until its domain, owner and data have been verified.

Routine reseller checks

  • Review resource use and suspended accounts.
  • Keep API keys restricted, rotated and stored securely.
  • Confirm backup coverage and test a restore procedure.
  • Remove access promptly when a staff member or integration no longer needs it.

Further guidance

Use the official InterWorx guides for SiteWorx packages and SiteWorx accounts. For billing automation, see our WHMCS integration guide.


Was this answer helpful?

« Back