Product attribute Package Name XXX Not Found on Server
If you use a cPanel & WHM server, you may encounter a Product attribute Package Name XXX not found on server
error in an email or in the Module Queue or Activity Log.
This error may occur if, for example:
- There are insufficient resources to create an account with the package.
- You have entered a package name in WHMCS incorrectly.
- An API token has insufficient permissions.
To identify the cause and resolve it, perform the steps below:
Insufficient Resources
The cPanel module can only provision accounts if your account has the necessary resources for the selected package.
To confirm that there are sufficient resources to create an account with this package directly in WHM:
- Log in to WHM.
- Go to WHM >> Account Functions > Create a New Account.
- For Choose a Package, ensure that the package does not include a (Cannot use due to limits) message. These packages do not have sufficient resources due to the limits that your hosting provider has set.
If your desired package appears with a (Cannot use due to limits) message, update the package to comply with your reseller account's limits. For more information about these limits, contact your hosting provider or system administrator.
Package Name Incorrect
You must enter the package name in WHMCS exactly as it appears in WHM.
To ensure this:
1. Log in to WHM.
2. Go to WHM >> Packages >> Edit a Package.
3. Copy the package name exactly:
4. Log in to WHMCS.
5. Go to Configuration > System Settings > Products/Services.
6. Edit the desired product.
7. In the Module Settings tab, click Switch to Advanced Mode.
8. Paste the package name into WHM Package Name.
9. Click Save Changes.
Insufficient API Token Permissions
The API token that you use to connect WHMCS to the cPanel & WHM server must have sufficient permissions.
To grant these permissions:
1. Log in to WHM.
2. Go to WHM >> Development >> Manage API Tokens.
3. Click Edit for the desired API token.
4. Ensure that all of the required API permissions are selected, including the list-pkgs
permission.
For a full list of required permissions, see API Token Permissions.
5. Click Save.