This forum is only for reproducible bugs with csf and lfd (i.e. not iptables problems, lack of understanding how to use a feature, etc). Posts must be accompanied with full technical details of the problem and how it can be recreated. Any posts not adhering to this, or not considered bugs, will be moved to the General Discussion (csf) forum.
It looks like there was a change in the cPanel ACLs of 'software' to 'thirdparty' - - going from version 66 to 68. The ACL that CSF tries to set is currently 'software-ConfigServer-csf', but the 'software' ACL is no longer available.
This has broken reseller access to the CSF UI in WHM.
If any additional information is needed, please let me know.
The mod_security v2 (apache) regex (line 335 of RegexMain.pm) has a bug that prevents it from working with IPv6 addresses.
The rule matches the first block in the log entry, which contains the source port appended to the client IP. The rule does attempt to remove this source port, but only does so if splitting the IP by the ':' character returns a list of size 2. Obviously, this won't work for...
I tried Fedora for the first time today, and CSF failed to install correctly (I've been successful with Centos for quite some time).
Basically the systemd unit files, and the binaries get placed with incorrect SELinux context. I fixed the contexts in /usr/lib/systemd/system/ before I could copy them, but in /usr/sbin they were erroneously:
With MESSENGERV2 and MESSENGER_HTTPS enabled, any time a SSL certificate path changes (which with AutoSSL could be any time the AutoSSL process runs), the csf.messenger.conf file is then pointing to a non-existant file, which causes Apache to throw a syntax error and not start.
Unfortunately, it seems like there isn't currently a cPanel hook that will always catch every instance of an SSL...
We have device names with a dash in them:
# ifconfig
eth-internet: flags=4163 mtu 1500
-- SNIP --
eth-local: flags=4163 mtu 1500
-- SNIP --
lo: flags=73 mtu 65536
-- SNIP --
eth-local is a management interface and I want it to be skipped by csf, so I set ETH_DEVICE_SKIP to eth-local, however during start csf reports that this is not valid:
*WARNING* ETH_DEVICE_SKIP device not listed in...
We are facing issue of LFD daemon failure regularly.
In WHM, it shows running and enabled, but failed to start.
Following is the error LFD generate:
>> Starting ConfigServer Firewall & Security - lfd...
>> Error: You have an unresolved error when starting csf. You need to restart csf successfully before starting lfd (see /etc/csf/csf.error)
>> PID file /var/run/lfd.pid not readable...
The Log Scanner Report emails contain lines of data from the log that appear to be continuations of previous multi-lined log entries.
It appears that the format of the log entries looks like:
-------------------------------
begin with the date/time in brackets
a space
the type of log entry ( info, warning, error)
a space
a source ( program or procedure ) of the log entry in brackets
a...
On my system (Debian 7) the day is padded with a space when the day is a single digit.
Then this line #262 in RegexMain.pm will not match:
if (($config{LF_FTPD}) and ($globlogs{FTPD_LOG}{$lgfile}) and ($line =~ /^\S+ \S+ \d+ \S+ \d+ \ \ FAIL LOGIN: Client (\S+) /)) {
Might be a typo. It works for all two digit days.
I changed it like that and it works: ^\S+ \S+\s+\d+ \S+ \d+ \ \ FAIL...
When using the webminmodule and the new fancy theme the csf page shows just a spinning wheel, nothing happens. When switching back to the old theme everythings works as expected.
What can I do?
I've got CSF and LFD csf v9.11 running on my VPS server without problems until a couple of weeks now.
Every couple of hours or sometimes a day LFD create a zombie defunct process on my Directadmin vps server.
When i restart LFD the zombie is gone a couple of hours but then its back again. Is this a bug in LFD?
Is there a way to debug LFD or do you have any idea where to look and to fix...
I noticed that the Log Scanner Report is not sent on a daily basis as it is configured. So one day i receive the report the other day I do not receive the report.
I observed this behaviour on two servers. I already removed CSF and re-installed it but no way. It still sends the reports randomly.
Checked also the crontab list but did not find any abnormalities.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum