ConfigServer Community Forum

Just following up to see if there's been any updates to this?

Good morning CSF Team! We are currently evaluating if we can use CloudLinux's Imunify360 solution which has a CSF Integration mode. In Imunify360, when it detects CSF blocked an IP, it will move that block from CSF to Imunify360, however it relies on the 'BLOCK_REPORT' function of CSF. During our te...

This has been fixed by Litespeed in the latest release.

Has there been any news to this? I'd like to get it fixed as well.

Found it - there was an entry in csf.allow for 10.0.0.0/0, which CSF was treating as 0.0.0.0/0

This issue is making me crazy -- however, one of our servers is accepting connections on all ports even though it's not specified in csf.conf, it's like iptables isn't even running, even though it is. Is there anything we can add to log all packets (and their iptables rule) so we can figure out why ...

It appears that the syntax error is gone, however my original problem (not related directly to the syntax error) is still there, so I guess I'll open up another ticket ;-) Just for my sanity, doing a upgrade which re-generates csf.conf, does it keep my existing values or do I need to go back and go ...

Got an updated config, still has a syntax error during run.

Don't have that in csf.conf.

# grep smtpauth -i /etc/csf/csf.conf
LF_SMTPAUTH = "5"
LF_SMTPAUTH_PERM = "1800"
# Tracking applies to LF_SSHD, LF_FTPD, LF_SMTPAUTH, LF_POP3D, LF_IMAPD,
SMTPAUTH_LOG = "/var/log/exim_mainlog"

It seems they are temp bans, however I'm not sure why they aren't displaying the port. 1409063893|89.254.152.80|,26|in|1800|lfd - (smtpauth) Failed SMTP AUTH login from 89.254.152.80 (LV/Latvia/-): 5 in the last 300 secs -- *ERROR* line:[1352] Command:[/sbin/iptables -v -A DENYIN ! -i lo -p tcp --dp...