{"id":767,"date":"2020-06-04T14:49:10","date_gmt":"2020-06-04T06:49:10","guid":{"rendered":"https:\/\/www.wesbytes.com\/guide\/?post_type=kb&p=767"},"modified":"2026-01-07T17:27:42","modified_gmt":"2026-01-07T09:27:42","slug":"tips-whm-cpanel-whm-access-restriction-for-certain-ip","status":"publish","type":"kb","link":"https:\/\/www.servergigabit.com\/guide\/kb\/tips-whm-cpanel-whm-access-restriction-for-certain-ip","title":{"rendered":"Tips WHM\/Cpanel: WHM Access Restriction for Certain IP"},"content":{"rendered":"

Tips WHM\/Cpanel: WHM Access Restriction for Certain IP<\/h4>\n

One of the common problems while managing WHM\/CPanel based hosting is blacklist access into WHM\/CPanel due to CPHulk plugins. CPHulk activated by default on WHM (if you choose Yes while initial setup) and serves as a blacklisted software just like Fail2ban or Denyhost to prevent logon services from spammers\/crackers.<\/p>\n

The problem is that CPHulk can\u2019t often decide which access is normal and which aren\u2019t. Consequently, due to so many failures, even our valid IP could be blacklisted or could not be logged in as root. Why? Because cracker will try to select a random password, and after a few logins attempt CPHulk will automatically reject root login.<\/p>\n

\"WHM\/Cpanel\"<\/p>\n

\n
In addition to closing the recommended port, there is also the easiest way to anticipate this kind of problem, by doing WHM access limit\/WHM login page access protection.<\/h6>\n

To top<\/i><\/a><\/p>\n<\/div>\n

To do so, run the following procedure :<\/p>\n

1. Login to WHM login page, enter your user name and password.
\n2. In the\u00a0Security Center<\/strong>\u00a0group menu, click\u00a0Host Access Control<\/strong>\u00a0menu.
\n3. On the\u00a0Daemon<\/strong>, select\u00a0Whostmgrd<\/strong>\u00a0daemon. It is a daemon application for WHM. We can also choose to protect SSH (SSHD<\/strong>) daemon or\u00a0CPaneld<\/strong>\u00a0daemon for CPanel.
\n4. In the\u00a0Access List<\/strong>, enter the IP or IP range that allows accessing. Write down the full subnet, for example, to network segment\u00a0122.201.98.70\/29<\/strong>\u00a0means to enter the IP\u00a0122.201.98.64\/255.255.255.248<\/strong>. Configure it as\u00a0122.201.98.64\/29<\/strong>\u00a0will not work because WHM will only accept full network subnet. If you asked, why using 122.201.98.64<\/strong>\/255.255.255.248 and not 122.201.98.70<\/strong>\/255.255.255.248 instead, then you should take the IP subnet course.
\n5. In the\u00a0Action<\/strong>\u00a0section select \u201cAllow<\/strong>\u201d.
\n6. Do the same thing to another IP segment which will be allowed.
\n7. At the bottom, Select\u00a0Daemon<\/strong>\u00a0=\u00a0Whostmgrd<\/strong>,\u00a0Access List<\/strong>\u00a0=\u00a0ALL<\/strong>\u00a0and\u00a0Action<\/strong>\u00a0=\u00a0Deny<\/strong>. Means that other than registered IP will not be allowed.
\n8. When finished, click the \u201cSave Host Access List<\/strong>\u201d.
\n9. Perform WHM access from the allowed IP and from outside registered IP list.<\/p>\n

For those who are accustomed to dealing with Linux servers<\/a>, the above process basically does limit access by adding a rule in the file \/etc\/hosts.allow<\/p>\n","protected":false},"excerpt":{"rendered":"

Tips WHM\/Cpanel: WHM Access Restriction for Certain IP One of the common problems while managing WHM\/CPanel based hosting is blacklist access into WHM\/CPanel due to CPHulk plugins. CPHulk activated by default on WHM (if you choose Yes while initial setup) and serves as a blacklisted software just like Fail2ban or Denyhost to prevent logon services from spammers\/crackers. The problem is…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"kbtopic":[32],"kbtag":[1604],"class_list":["post-767","kb","type-kb","status-publish","hentry","kbtopic-whm","kbtag-whm-cpanel"],"_links":{"self":[{"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kb\/767","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kb"}],"about":[{"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/types\/kb"}],"author":[{"embeddable":true,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/comments?post=767"}],"version-history":[{"count":3,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kb\/767\/revisions"}],"predecessor-version":[{"id":5236,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kb\/767\/revisions\/5236"}],"wp:attachment":[{"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/media?parent=767"}],"wp:term":[{"taxonomy":"kbtopic","embeddable":true,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kbtopic?post=767"},{"taxonomy":"kbtag","embeddable":true,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kbtag?post=767"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}