Restricting a management service through WHM Host Access Control

Confirm root-level authorisation, a working out-of-band console and the exact trusted IPv4 and IPv6 sources. Save current rules and identify monitoring or integrations that need continued access.

1. Open Host Access Control and review whether the interface uses service names or port/protocol rules on this operating system.
2. Add explicit allow rules for the required trusted administrative sources before any broader reject or drop rule. Include the real management port and necessary address family.
3. Check the installed firewall integration. On some configurations another firewall application can override or bypass this interface’s expected rule handling.
4. Apply a narrow restriction for one service and test a new connection from an allowed source before ending the current session.
5. Verify the expected rejection from an authorised external test source, and confirm unrelated public website or mail services remain accessible.

The intended management service should remain reachable from approved networks while the restricted sources are denied. Record the effective rule order and tested recovery route.

If access is lost, use the established console recovery path and restore the saved rule set with administrator assistance. Do not repeatedly add broader rules without knowing which firewall is active. A dynamic home IP may change and make a permanent allowlist unreliable.

No. WHM management access and an application’s public login endpoint are different services. Apply appropriate application and web-firewall controls for the website separately.

• Reviewing cPHulk login blocks without weakening global protection
• Planning key-based administrator access before disabling SSH passwords
• Enabling two-factor authentication for WHM administration
• Restricting compiler access to accounts that require it

• cPanel: Host Access Control