You can find our user documentation at

Check out our new API beta site!

Child pages
  • Host Access Control
For cPanel & WHM version 76

Skip to end of metadata
Go to start of metadata

(WHM >> Home >> Security Center >> Host Access Control)



If you accidentally lock yourself out of WHM when you use this interface, edit the /etc/hosts.allow file through the command line to regain access.


The Create Support Ticket interface (WHM >> Home >> Support >> Create Support Ticket) automatically adds cPanel Support's IP addresses to the server's /etc/hosts.allow file. For more information, read our Create Support Ticket documentation.

Use this interface to allow or deny (block) access to the following services for specific IP addresses:
  • cPanel (cpaneld)
  • WHM (whostmgrd)
  • Webmail (webmaild)
  • Web Disk (cpdavd)
  • FTP (ftpd)
  • SSH (sshd)
  • SMTP (smtp)
  • POP3 (pop3)
  • IMAP (imap)


  • To control access to the ftpd daemon, you must use the ProFTPD FTP server. Pure-FTP does not support TCP wrappers.
  • To control access to the POP3 or IMAP services, you may use the Dovecot® mail servers.

Allow or deny access for an IP address

To allow or deny an IP address to access a service, perform the following steps:

  1. Enter the service name in the daemon text box.
  2. Enter the IP address or hostname in Access List text box. 
    • You may enter wildcards in this text box.
    • You cannot enter a range of IP addresses with CIDR notation.
    • To specify a network range, add a network mask to the IP address.
      • For example,, where is the desired network mask you want to use.
  3. Enter the desired action in the Action text box.
    • Enter allow to allow access.
    • Enter deny to deny access.
  4. Describe the rule in the Comment text box.
  5. Click Save Host Access List, or click  Reload  to delete any changes.


You can also enter ALL EXCEPT IP address in the Access List text box. When you enter allow as your action, the system will allow all of the addresses except for addresses that you entered in the Access List text box.

Allow or deny IP addresses on the command line

For greater host access control flexibility, you can create rules in the command line. To do this, perform the following steps:

  1. Log in to your server as the root user.
  2. Open the /etc/hosts.allow file with your preferred text editor.
  3. Enter the desired rules in the following format:

     service : IP address : action

    See the following example to allow IP address to access the cPanel service:

    cpaneld : : allow


  • When you configure your firewall directly, you can use CIDR notation.
  • WHM does not use a hosts.deny file. Add deny statements to the /etc/hosts.allow file.

CentOS, CloudLinux™, or Red Hat® Enterprise Linux (RHEL) 6, or Amazon Linux

On a CentOS, CloudLinux, or RHEL 6, or Amazon® Linux system, use the iptables utility to manage your firewall.

  • You can block a specific IP address with the iptables command. For example, to block, run the following command:

    iptables -A INPUT -s -j DROP 
  • You can block a specific port for an IP address. For example, to block port 23 on, run the following command: 

    iptables -A INPUT -s -p tcp --destination-port 23 -j DROP

CentOS 7, CloudLinux 7, or RHEL 7

On a CentOS 7 or CloudLinux 7 system, use the firewalld utility to manage your firewall.

For example, to block traffic for a single IP address, run the following command, where is the IP address that you wish to block:

firewall-cmd --add-rich-rule='rule family="ipv4" source address="" drop' --permanent

For more information, read Red Hat's firewalld documentation.

Additional notes

You must enter your allow rules before your deny rules. For example, to allow access for two IP addresses, but deny access from all other addresses, use either of the following methods:

Create two separate rules:

  • Create one rule that allows
  • Create a second rule that denies access to ALL IP addresses.

Create one rule:

  • Enter all except in the Access List text box.
  • Enter denyin the Action text box.

Additional documentation

There is no content with the specified labels

There is no content with the specified labels

There is no content with the specified labels