WHM offers controls for restricting service access and preventing repeated login attempts. This guide explains how to block an identified source address and choose the appropriate control.
Check the source and retain recovery access
Confirm the address in relevant logs. Keep console access available and do not block your management address. Blocking an IP does not guarantee protection against distributed attacks.
Use Host Access Control
Open Security Center > Host Access Control.
On CloudLinux, AlmaLinux and Rocky Linux, enter the service’s port, source IP or CIDR, and TCP or UDP protocol. Select DROP or REJECT, then Add Rule and check the applied list. Enter necessary ACCEPT rules before blocking rules. Do not assume a blank port means every service.
On Ubuntu, the interface instead uses a daemon name, access list and deny action. Save using Save Host Access List. Use the procedure matching your server’s operating system.
Other firewall applications may affect whether these rules are used; confirm the active firewall with the administrator.
Use cPHulk for login restrictions
-
Open Security Center > cPHulk Brute Force Protection.
-
Confirm protection is enabled and review the login-protection settings.
-
Add the address and a reason under Blacklist Management, then save.
cPHulk restricts authentication to protected services. It is not equivalent to a blanket network block. Test the intended restriction and review it when the address no longer needs blocking.



