Workaround for Configurable Package Addon not working after cPanel v76

[DennisHermannsen]

Hi,

We became aware of an issue with the Configurable Package Addon after updating to cPanel v76. After discussing with both cPanel and WHMCS about this, it seems to be a result of this change in cPanel:

Quote

Fixed case CPANEL-21931: Verify existence of package when creating an account.

https://documentation.cpanel.net/display/CL/76+Change+Log

When creating a new account that would be using the 'Custom' package (that doesn't exist in WHM), you'd get the following error:

Quote

Sorry, “username_Custom” is not a valid package name. at /usr/local/cpanel/Whostmgr/Accounts/Create.pm line 1155.

 

To fix the issue, you need to create the Custom package on each cPanel server in WHM. If you set everything to Unlimited and only have configured Disk Space in WHMCS, you'll end up with a cPanel account that has a limited disk space but unlimited resources of everything else. Make sure to set static values for every option in WHM that are not configurable by the Configurable Package Addon.

[WHMCS Marcus]

This was not necessarily caused by the change in v76. If you have a valid package called "Custom" in all of your WHM instances, this will continue to work. If you do not, after v76 implemented the package existence verification would prevent the API from being able to create the account.

In any regard, you must ensure you have the proper permissions for packages and one thing that trips up many customers is the API permission for viewglobalpackages. If you create a package as a root user in WHM, you can name it literally anything you want. If you create it as a reseller user, the package will always be named username_packagename. If you do not have the viewglobalpackages permission enabled, the WHM API will only list things that match username_xxxxxxx even if the API Token was created under the root user's account.