Version 72 Documentation
Child pages
  • Installation Guide - Troubleshoot Your Installation
For cPanel & WHM version 72
Skip to end of metadata
Go to start of metadata

Overview

This documentation describes additional steps to use if you install cPanel & WHM with this guide, but still experience problems.

Remember:

License errors

Problem

You see license errors during or after the installation process (for example, a License File Expired message).

Explanation

Your license may be expired or improperly configured, or your system may not connect properly to the cPanel, Inc. license servers.

Solution

To check your cPanel license, perform the following steps:

  1. Run either of the following commands to obtain your license's IP address:

    curl -L http://cpanel.net/showip.cgi
lynx -dump http://cpanel.net/showip.cgi
  2. Navigate to the cPanel License Verification page.

  3. Enter the IP address that you obtained in Step 1. Our website will display the status of your license.

    Notes:

    • The License Verification page lists licenses for cPanel and other products separately. The list sorts each license from newest to oldest. For example, you may see COMPANYNAME-INTERNAL and COMPANY-CLOUDLINUX-INTERNAL-WITH-CPANEL in the Package column, where COMPANYNAME represents the name of the partner that issued the license. This example indicates that your server possesses a cPanel license and a CloudLinux license that you purchased through cPanel, Inc. Your CloudLinux license may report an active status while your cPanel license reports as expired.
    • If the most recent license for a product contains an expired status, renew your license through the cPanel Store or contact cPanel Customer Service for further assistance.
    • If your server’s IP address does not match the IP address on your license, contact cPanel Customer Service for further assistance.

  4. If your IP address matches the license, and you still experience problems, run the following script to verify your license:

    /usr/local/cpanel/cpkeyclt

    After the script runs, the command line will display no messages if your license works properly. If the script requires more than a few seconds to run, your server may have encountered connectivity issues.

  5. If the /usr/local/cpanel/cpkeyclt script fails, ensure that our licensing servers resolve. To test that you can resolve our servers, run the following command:

    host auth.cpanel.net

    You may also need to ensure that the time and date of the server are not set too far in the future or past.

Perl installation errors

Problem

You see the following error message during the installation process:

Fatal! Perl must be installed before proceeding!
Explanation

Perl must exist on your server before the installation script for cPanel & WHM can run successfully. If Perl does not exist during installation, the cPanel & WHM installer attempts to install Perl via the yum -y install perl command. If the installation does not succeed, the system displays this error message.

  • We strongly recommend that you allow your operating system's distribution to control the system Perl installation. Do not customize this Perl installation.
  • For more information about Perl on your server, and which versions of Perl ship with specific operating systems, read our Guide to Perl in cPanel & WHM documentation. cPanel & WHM servers use multiple Perl environments.
Solution

Problems with yum generally cause this error. Make certain that yum functions properly on your server.

To attempt to install Perl again, run the following command:

yum install perl

High CPU load on Hyper-V

Problem

The server reports a high CPU load, and Hyper-V's Dynamic Memory option is enabled.

Explanation

This problem is due to an issue with sleep interruptibility in Hyper-V.

Solution

For more information and a patch to fix the issue, visit the LKML website.

RPM installation failures

Problem

One or more RPMs fail during installation.

Explanation

There are several reasons why your operating system's RPM installations may fail.

Solution

For steps to fix this issue, read our RPM Installation Failures documentation.

 DNS problems

Problem

You experience problems that relate to DNS.

Explanation
  • You may need to set up resolvers. Resolvers allow your server to communicate with DNS servers to find IPv4 or IPv6 addresses that correspond to domain names.
  • One or more directories or partitions may be improperly configured.
Solution

To check your server's resolvers, run the following command, where example.com represents a domain on your server:

host example.com

If this command did not return results, the /etc/resolv.conf file does not contain resolvers. Use WHM's Resolver Configuration interface (Home >> Networking Setup >> Resolver Configuration) to add resolvers to your server.

To determine whether your server can communicate with a resolver, perform the following steps:

  1. Use SSH to log in to your server via the command line.

  2. Run the following commands to check communication via IPv4 and IPv6:

    ping 8.8.8.8
ping6 2001:4860:4860::8888

  3. If these commands fail, make certain that you used the correct IP addresses. Then, run the following commands to find the problem:

    traceroute 8.8.8.8
traceroute6 2001:4860:4860::8888

Notes:

  • Replace 8.8.8.8 with the desired resolver's IPv4 address.
  • Replace 2001:4860:4860::8888 with the desired resolver's IPv6 address.

Hostname issues

Problem

A cloud-hosted server does not retain the hostname setting.

Explanation

The dhclient script that the cloud hosting provider uses may interfere with cPanel & WHM's hostname configuration script.

Solution

For steps to fix this issue, read our Cloud-Hosted Hostname Solution documentation.

Additional documentation