CSF banning cloudflare ip

Operating System & Version
Centos 7.7
cPanel & WHM Version
v86.0.18

Luntyr

Registered
Apr 22, 2020
4
1
3
New York
cPanel Access Level
Root Administrator
Hello,

I'm experiencing a bug using CSF on cpanel CENTOS 7.7 [srv] v86.0.18 that is banning cloudflare ips.
I have enabled mod_cloudflare and it's working because I can see the real ip address of requests on Apache Status, but CSF is always banning cloudflare ip.
I also have enabled for the website that is getting flood and ddos attack cloudflare ban ip but I can't see that any ip address was added from the firewall.

How can I fix this issue because it's making me crazy, cloudflare doesn't block the attackers.
 

GOT

Get Proactive!
PartnerNOC
Apr 8, 2003
1,739
305
363
Chesapeake, VA
cPanel Access Level
DataCenter Provider
Add the cloudflare IP ranges to the /etc/csf/csf.ignore file

 

Luntyr

Registered
Apr 22, 2020
4
1
3
New York
cPanel Access Level
Root Administrator
Add the cloudflare IP ranges to the /etc/csf/csf.ignore file

I've already whitelisted cloudflare ip but it isn't trying to ban the attacker anymore which indicates that the csf is still getting cloudflare ip.
I have enable cloudflare api and configured with the cloudflare api but it isn't working. I have also enabled mod_cloudflare, and the apache logs show the real ip but the csf is still getting the cloudflare ip.
 

GOT

Get Proactive!
PartnerNOC
Apr 8, 2003
1,739
305
363
Chesapeake, VA
cPanel Access Level
DataCenter Provider
It does not good to ban the attacker, the network level will never see the origin IP and as such, blocking them would do not good. If you want to block based on origin IP you have to do that at the cloudflare level.
 

vacancy

Well-Known Member
Sep 20, 2012
433
137
93
Turkey
cPanel Access Level
Root Administrator
Csf takes action by reading netstat data. mod_cloudflare/mod_remoteip is a webserver module, csf cannot process IP addresses read by mod_cloudflare/mod_remoteip.

Also, since the traffic in to your server comes via cloudflare, it is useless to banning your real ip addresses from the server, you should ban these ip addresses via cloudflare.
 
Last edited:

cPanelLauren

Product Owner
Staff member
Nov 14, 2017
13,295
1,255
313
Houston
You also may want to look at switching from mod_cloudflare since it's no longer supported or maintained by CloudFlare

https://support.cloudflare.com/hc/en-us/articles/200170916-Restoring-original-visitor-IPs-Option-1-Installing-mod-cloudflare said:
Cloudflare no longer updates and supports mod_cloudflare, starting with versions Debian 9 *and *Ubuntu 18.04 LTS of the Linux operating system. We now support mod_remoteip for customers using Apache web servers. Customers who are interested in building the mod_cloudflare package can download the codebase from GitHub.
mod_remoteip is the recommended method for this now and I wrote a pretty detailed how-to on this not very long ago which you can find here: Easiest way to install mod_cloudflare on latest CPanel since it's not available in EA?

Also, ConfigServer Firewall Comes prebuilt with CloudFlare IP's integrated this is detailed in Section 27 of their readme.txt file:

https://download.configserver.com/csf/readme.txt said:
27. CloudFlare
##############

This features provides interaction with the CloudFlare Firewall.

As CloudFlare is a reverse proxy, any attacking IP addresses (so far as
iptables is concerned) come from the CloudFlare IP's. To counter this, an
Apache module (mod_cloudflare) is available that obtains the true attackers
IP from a custom HTTP header record (similar functionality is available
for other HTTP daemons.

However, despite now knowing the true attacking IP address, iptables cannot
be used to block that IP as the traffic is still coming from the CloudFlare
servers.

CloudFlare have provided a Firewall feature within the user account where
rules can be added to block, challenge or whitelist IP addresses.

Using the CloudFlare API, this feature adds and removes attacking IPs from that
firewall and provides CLI (and via the UI) additional commands.

There are several restrictions to using this feature:

1. All lfd blocks will be temporary blocks so that csf/lfd can keep blocks in
sync with CloudFlare

2. Automatic blocks via lfd are limited to LF_MODSEC and LF_CXS triggers as
only through these can the domain name be determined. Any users that own
domains that are involved in the trigger will get a block in their
CloudFlare Firewall. Additionally, any users with the special case "any"
will also get blocks

3. The temporary/permanent config of the lfd settings are ignored and CF_TEMP
is used instead

4. LF_TRIGGER must not be used, the feature will not work with it enabled

5. mod_cloudflare or similar must be used to report real IP in the Apache logs

6. URLGET must be set to 2 (i.e. LWP) must be used

7. If PERMBLOCK is used, the last tempblock will remain and never be cleared.
So any CloudFlare Firewall entries must be manually cleared in CloudFlare
or via CLI

8. There are restrictions imposed by CloudFlare to the number of rules that
can be created depending on the type of account used. See
https://goo.gl/ssGu7v for more information

9. When restarting csf, any old temporary blocks will still be created for lfd
to clear when it restarts

10. All interaction with CloudFlare is at User-level, not Zone-level

11. If using the CloudFlare cPanel user plugin, it must be v7+

CF_TEMP should be configured taking into account the maximum number of rules
that the CloudFlare account allows: https://goo.gl/ssGu7v

All CloudFlare users for the domains that are involved in LF_MODSEC and
LF_CXS triggers will have a CloudFlare rule added. Any CloudFlare account
configured to use the special case "any" field value in csf.cloudflare will
have a CloudFlare rule added regardless of domain.

NOTE: You should always list the CloudFlare IP addresses in /etc/csf/csf.ignore
to prevent them from being blocked by lfd from IP Ranges | Cloudflare
 

Luntyr

Registered
Apr 22, 2020
4
1
3
New York
cPanel Access Level
Root Administrator
Csf takes action by reading netstat data. mod_cloudflare/mod_remoteip is a webserver module, csf cannot process IP addresses read by mod_cloudflare/mod_remoteip.

Also, since the traffic in to your server comes via cloudflare, it is useless to banning your real ip addresses from the server, you should ban these ip addresses via cloudflare.
I wanted to configure it automaticaly with the cloudflare api. I just need the CSF to get the real ip address so it will send it to the cloudflare firewall. I couldn't figure it out because it was always reading only cloudflare ips.
Is there any way for the csf to get the real attacker ip address so I can ban him through the cloudflare firewall using their API?
 

Luntyr

Registered
Apr 22, 2020
4
1
3
New York
cPanel Access Level
Root Administrator
You also may want to look at switching from mod_cloudflare since it's no longer supported or maintained by CloudFlare



mod_remoteip is the recommended method for this now and I wrote a pretty detailed how-to on this not very long ago which you can find here: Easiest way to install mod_cloudflare on latest CPanel since it's not available in EA?

Also, ConfigServer Firewall Comes prebuilt with CloudFlare IP's integrated this is detailed in Section 27 of their readme.txt file:
I'll try that as soon as possible and give you a feedback!
 
  • Like
Reactions: cPanelLauren