Common Errors in cPanel and WHM
Download as PPTX, PDF0 likes237 views
The document outlines common errors encountered in cPanel and WHM, such as 'access denied' and 'login failed', along with the necessary steps to resolve each issue. It emphasizes the importance of correct configurations, valid package names, and ensuring proper user permissions. Additionally, it highlights compatibility issues with different versions of WHMCS and cPanel, indicating the need for updates in certain cases.
Common Errors in cPanel and WHM
- 1. Common Errors in cPanel and WHM
- 2. Table of Contents 2 Access Denied You do not have permission to use Selected Package Package Not Allowed or Exceeded Resource/Account Allocation Resellers are not permitted to create subdomains of the server’s main domain Unable to validate settings for language: English Sorry, that username is reserved Sorry, a group for that username already exists Login Failed No user name supplied: “username” is a required argument Action Failed Unable to auto- login. Please contact support WHM Username is missing for the selected server An Unknown Error Occurred after updating to cPanel 74 Product attribute Package Name “Package Name” not found on server
- 3. The error, Access Denied, indicates that WHMCS was denied access by the cPanel server to perform the action that had been requested. The following points need to be ensured in order to investigate and resolve this error: Those server settings are valid which are configured inWHMCS. The API credentials have the necessary permissions for performing the desired action. The Username and Server assignment under the tab for client’s Products/Services in WHMCS match with cPanel’s account records. The user specified on the server settings page has adequate permissions for managing the cPanel hosting account. 3 Access Denied
- 4. You need to correct the Packages Name setting if you receive this error while trying to create an account. For this purpose, you need to go to Configuration > System Settings > Products/Services. When asked for the WHM Package Name, you need to enter it exactly as it appears in WHM. It should be in the format username_packagename. 4 You do not have permission to use Selected Package
- 5. When you get this error, it most likely means that you have only reseller access to your server and that you are attempting to create an account without a valid package name.You must ascertain that the WHM Package Name that is in WHMCS’ product configuration matches with the one that has been set up in your WHM Package Editor. 5 Package Not Allowed or Exceeded Resource/Account Allocation
- 6. 6 1-800-123 -8156 Whoa!That’s a big number, aren’t you proud?
- 7. This error indicates that no domain has been selected and that it is missing. You need to ensure the product has domain name entered. You might need to enable Require Domain in Configuration > System Settings > Products/Services. 7 Resellers are not permitted to create subdomains of the server’s main domain
- 8. cPanel & WHM has made many changes in their latest version’s API, which are not backwards compatible. Hence, it isn’t possible to use an older version of WHMCS with the latest version of cPanel.You must upgrade your WHMCS install to version 4.2.1 or higher. 8 Unable to validate settings for language: English
- 9. The phrase, “test”, and certain other phrases, are not allowed to be present in the usernames by cPanel & WHM. When this error is encountered, you should change the username and run the Create Module Command again.You can find the username under the client’s products/services tab. 9 Sorry, that username is reserved
- 10. When this error is encountered, it means that an account with that username already exists on the server.This error has been found to occur on shared servers. Even when one doesn’t have an account with that username under one’s reseller account, some other reseller on the same server might be using it.To resolve the issue caused by this error, you need to navigate to the client’s Products/Services tab, and then change the Username. Next, you need to click Save Changes. Finally, you must click the “Create” Module Command button. 10 Sorry, a group for that username already exists
- 11. When you get this error, there can be two reasons for it, which are being mentioned below. Incorrect login details under Configuration > System Settings > Servers. You must ensure that you are using either the username and API Key or the username and password combination. You must also ensure that the login details are accurate. The settings for Brute Force Protection are not letting WHMCS create/suspend/terminate accounts via the cPanel API. In this case, you need to adjust the BFP settings in WHM. 11 Login Failed
- 12. This error indicates an empty username, under the client’s Products/Services tab. In such a situation, you need to enter a username. Then save the changes and subsequently try module creation again. Additionally, you must ensure that Require Domains is checked in Configuration > System Settings > Products/Services. 12 No user name supplied:“username” is a required argument
- 13. This error indicates an empty username, under the client’s Products/Services tab.You must enter a username, then save changes, and finally try module creation again. Moreover, you must ensure that Require Domains is checked in Configuration > System Settings > Products/Services. 13 Action Failed Unable to auto-login. Please contact support
- 14. This error is caused by a server balancing misconfiguration. In this case, there isn’t any server that has been selected for account creation. 14 WHM Username is missing for the selected server
- 15. Every module command that is performed after an update to cPanel 74, will result in an error message, “An unknown error occurred”. Inspection of the Module Debug Log reveals aWHM 404 error page being returned by the server.The cause for it is deprecation of the cPanel XML API in the version 74. If you want to use the newer cPanel JSON API, then you must update toWHMCS 7.3 or higher. 15 An Unknown Error Occurred after updating to cPanel 74
- 16. There can be two reasons why this error occurs.These are- Insufficient resources for package creation. The entered package name must be exactly the same as defined in WHM. 16 Product attribute Package Name “Package Name” not found on server