WHM Password Keeps Failing: cPHulk Lockout Fix

If your WHM root password works after a reset but stops working again after a few hours or days, the password may not actually be changing. In many cases, cPHulk Brute Force Protection is blocking your IP address after too many failed login attempts.

This can make a correct password appear to be invalid. Instead of repeatedly resetting the root password, check whether cPHulk is responsible and whitelist the IP addresses you regularly use.


What Is Actually Happening?

WHM and cPanel include a security feature called cPHulk Brute Force Protection. It monitors login attempts and can temporarily block an IP address when too many authentication failures occur.

With the default settings, cPHulk can block an IP after:

  • 5 failed attempts within 5 minutes
  • 30 failed attempts within 24 hours

Once your IP is blocked, WHM may return an HTTP 401 Unauthorized response even when you enter the correct password. This can easily look like a password problem.

Resetting the password may allow you to log in temporarily, but the same lockout can happen again when cPHulk reaches its failure limit.


Why Does cPHulk Keep Blocking the IP?

1. Automated Login Attempts

Servers with public IP addresses regularly receive automated login attempts from compromised systems and bots. Some of these attempts may target SSH, while others can target WHM on port 2087.

Repeated failed attempts can increase the failure count until cPHulk blocks the source IP.

2. Saved or Incorrect Passwords

Browsers, password managers, scripts, or monitoring tools may still have an old password saved. Even a small number of unsuccessful login attempts can contribute to the cPHulk limit.

3. Multiple Users or Devices

If several people access WHM through the same office, home, VPN, or NAT IP address, failed login attempts from one user can affect everyone using that IP.


How to Check if cPHulk Is Blocking You

Connect to your server through SSH as root and check the cPHulk login tracking database:

Terminal
sqlite3 /var/cpanel/hulkd/cphulk.sqlite \
  "SELECT USER, NOTES, datetime(EXPTIME, 'unixepoch') AS expires \
   FROM login_track WHERE TYPE = -3 ORDER BY LOGINTIME DESC LIMIT 20;"

Look through the results for entries showing IP reached maximum auth failures. If your current IP address appears in the blocked entries, cPHulk is likely responsible for the WHM login problem.


Permanent Fix: Whitelist Your Trusted IP Addresses

If you regularly access WHM from a fixed office, home, VPN, or support IP, you can add those trusted addresses to the cPHulk whitelist.

To whitelist one IP address:

Terminal
/usr/local/cpanel/scripts/cphulkdwhitelist <your-ip>

You can also whitelist an IP range when your trusted network uses a subnet:

Terminal
/usr/local/cpanel/scripts/cphulkdwhitelist 1.2.3.0/24

Repeat the command for each trusted location from which you normally manage your server:

Terminal
/usr/local/cpanel/scripts/cphulkdwhitelist <your-office-ip>
/usr/local/cpanel/scripts/cphulkdwhitelist <your-home-ip>

To find your current public IP address, you can visit icanhazip.com in your browser.

Only whitelist IP addresses that you trust and control. Avoid adding large public IP ranges unnecessarily, as this reduces the protection provided by cPHulk.


Reduce False Lockouts with cPHulk Settings

If multiple administrators or customers legitimately access WHM from different IP addresses, you may want to adjust the cPHulk failure limits.

In WHM, go to:

Home → Security Center → cPHulk Brute Force Protection → Configuration Settings

For environments with multiple legitimate users, the following settings can reduce unnecessary lockouts:

  • Maximum Failures by IP Address (per One Day): 100
  • Maximum Failures by IP Address (per Brute Force Period): 15
  • Brute Force Protection Period: 5 minutes

The default values are 30 daily failures and 5 failures during the brute-force period. Keep in mind that increasing these limits can also reduce the sensitivity of brute-force protection.


What to Do If You Are Locked Out of WHM

If you cannot access WHM because your IP has been blocked, you can normally resolve the issue through SSH.

  1. Connect to the server through SSH as root.
  2. Whitelist your current public IP address.
  3. Try accessing WHM again.
Terminal
/usr/local/cpanel/scripts/cphulkdwhitelist <your-ip>

After the IP is whitelisted, try logging in to WHM again using the correct root credentials.

If SSH access is also unavailable, use the server console provided by your VPS or dedicated server provider. Many hosting providers offer a web-based console that can be used when normal SSH access is not available.


Check for Other Sources of Failed Logins

If cPHulk repeatedly blocks your IP even after you whitelist it, look for applications or devices that may still be using an incorrect password.

Common sources include:

  • Saved passwords in browsers or password managers
  • Old credentials stored in automation scripts
  • Monitoring systems checking WHM or server services
  • Other administrators using outdated credentials
  • VPN connections that change your public IP address
  • Automated tools repeatedly attempting authentication

If you suspect that an unknown person has actually gained access to the server, treat the situation as a security incident. Review authentication logs, secure SSH access, check authorized keys, and rotate affected credentials.


When to Contact ServerLicenser Support

Contact ServerLicenser Support if:

  • You have whitelisted your IP but WHM continues to reject the correct password.
  • You are repeatedly locked out even though there are no obvious failed login sources.
  • You suspect unauthorized access to the server.
  • You need help reviewing cPHulk settings across multiple servers.
  • You cannot access either WHM or SSH and need help determining the next step.

Quick Troubleshooting Checklist

  • Confirm that you are using the current root password.
  • Check whether cPHulk has blocked your IP.
  • Whitelist your trusted public IP address.
  • Check browsers and password managers for outdated credentials.
  • Review scripts and monitoring tools for repeated failed logins.
  • Adjust cPHulk limits if your environment has many legitimate users.
  • Investigate possible unauthorized access if lockouts continue.

Bottom Line

If you repeatedly reset the root password because WHM suddenly rejects it, do not assume that the password is changing. cPHulk may simply be blocking your IP after repeated authentication failures.

Check the cPHulk records, whitelist your trusted IP addresses, and review the source of failed login attempts. This can prevent the recurring cycle of resetting the root password.


Related Articles

Was this answer helpful? 0 Users Found This Useful (0 Votes)