WHM Password Keeps Changing? Fix cPHulk Lockouts
If you reset your root password, successfully log in to WHM, and then find that the same password stops working a day or two later, the password may not actually be changing.
In many cases, cPHulk Brute Force Protection is blocking your IP address because of repeated failed login attempts. This makes a correct password appear to be invalid.
Instead of repeatedly changing the root password, check cPHulk first 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 authentication attempts and can automatically block an IP address after too many failed logins.
With the default configuration, cPHulk can block an IP after:
- 5 failed attempts within 5 minutes
- 30 failed attempts within 24 hours
When your IP is blocked, WHM can return an HTTP 401 Unauthorized response even if you enter the correct password.
This can look exactly like a wrong-password problem. You may reset the root password, successfully log in, and then become locked out again later when cPHulk reaches its failure limit.
Why Does cPHulk Keep Locking You Out?
There are several common reasons for repeated cPHulk lockouts.
1. Automated Login Attempts
Servers with public IP addresses are frequently targeted by automated login attempts. Attackers and compromised systems can repeatedly try different credentials against services such as SSH and WHM.
Repeated failed attempts can increase the cPHulk failure count and eventually trigger an IP block.
2. Saved or Incorrect Credentials
Your browser, password manager, script, or monitoring system may still have an outdated password saved. These unsuccessful attempts can contribute to the cPHulk failure threshold.
3. Multiple Users Sharing One IP
If several people use the same office, home, VPN, or NAT IP address, failed login attempts from one person can affect everyone using that public IP.
How to Confirm That cPHulk Is the Cause
Connect to your server through SSH as root and check the cPHulk login records:
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 for entries containing IP reached maximum auth failures. If your current IP address appears in the blocked records, cPHulk is likely responsible for the WHM login problem.
Permanent Fix: Whitelist Your Trusted IPs
If you regularly manage your server from a trusted office, home connection, VPN, or other fixed location, add those IP addresses to the cPHulk whitelist.
To whitelist a single IP address:
/usr/local/cpanel/scripts/cphulkdwhitelist <your-ip>
To whitelist an IP range, use the subnet format:
/usr/local/cpanel/scripts/cphulkdwhitelist 1.2.3.0/24
For example, you can whitelist each trusted location separately:
/usr/local/cpanel/scripts/cphulkdwhitelist <your-office-ip>
/usr/local/cpanel/scripts/cphulkdwhitelist <your-home-ip>
You can find your current public IP address by visiting icanhazip.com in your browser.
Only whitelist IP addresses that you trust. Avoid unnecessarily whitelisting large networks because doing so can reduce the protection provided by cPHulk.
Tune cPHulk to Reduce False Lockouts
If several staff members or customers legitimately access WHM from different IP addresses, increasing the failure limits may help reduce unnecessary lockouts.
In WHM, open:
Home → Security Center → cPHulk Brute Force Protection → Configuration Settings
For shared or multi-user environments, the following settings can provide more tolerance for failed login attempts:
- Maximum Failures by IP Address (per One Day): 100 (default: 30)
- Maximum Failures by IP Address (per Brute Force Period): 15 (default: 5)
- Brute Force Protection Period: 5 minutes (default)
Increasing these values can reduce false-positive lockouts, but it also makes cPHulk less aggressive against repeated authentication failures. Choose values appropriate for your server environment.
What to Do If You Are Locked Out Right Now
If you cannot access WHM because your IP has been blocked, you can normally use SSH to whitelist your IP.
- Connect to the server through SSH as root.
- Whitelist your current public IP address.
- Try logging in to WHM again.
/usr/local/cpanel/scripts/cphulkdwhitelist <your-ip>
After the IP has been whitelisted, try accessing WHM again with your current root credentials.
If SSH is also unavailable, use the web-based server console provided by your VPS or dedicated server provider. A provider console can give you direct access when normal SSH connectivity is unavailable.
Check for the Source of Failed Login Attempts
If the lockout continues, identify what is generating the failed authentication attempts. Common causes include:
- Old passwords saved in browsers or password managers
- Automation scripts using outdated credentials
- Monitoring applications making repeated login attempts
- Another administrator using an old password
- VPN connections that frequently change the public IP
- Automated internet-based login attempts
Finding and correcting the source of failed attempts is important. Whitelisting your IP alone does not address the underlying cause.
What If You Suspect Unauthorized Access?
If you believe someone has actually gained access to the server, treat the issue as a security concern rather than a normal cPHulk lockout.
Review authentication activity, check SSH access, inspect authorized keys, and rotate affected credentials as appropriate.
The SSH authorized keys file for the root account is:
/root/.ssh/authorized_keys
When to Contact ServerLicenser Support
Contact ServerLicenser Support if:
- You have whitelisted your IP but WHM continues rejecting the correct password.
- You are repeatedly locked out without an obvious source of failed logins.
- You suspect unauthorized access to the server.
- You need help reviewing cPHulk settings on multiple servers.
- You need assistance troubleshooting repeated authentication failures.
Quick Troubleshooting Checklist
- Confirm that you are using the current root password.
- Check cPHulk for blocked IP addresses.
- Whitelist your trusted public IP.
- Check saved passwords in browsers and password managers.
- Review automation and monitoring tools for outdated credentials.
- Check whether multiple users are sharing the same public IP.
- Adjust cPHulk thresholds if your environment requires higher limits.
- Investigate possible unauthorized access if the problem continues.
Bottom Line
If you repeatedly reset the root password because WHM suddenly rejects it, the password may not be the problem. cPHulk can block your IP after repeated failed authentication attempts, making the correct password appear to be wrong.
Check the cPHulk records, whitelist trusted IP addresses, and identify the source of failed login attempts. This can stop the recurring cycle of resetting your WHM root password.
Related Articles
- Remove the WHM Critical Security Update Banner (4 Steps) — Troubleshoot the critical security update notification in WHM.
- cPanel License Fails After CSF or Firewall Restart — Fix — Troubleshoot license problems after a CSF or firewall restart.
- Browse All Troubleshooting Articles
