https://bugs.contribs.org/show_bug.cgi?id=10608
Bug ID: 10608
Summary: Incorrect jail.conf entry for nextcloud
Classification: Contribs
Product: SME Contribs
Version: 9.2
Hardware: ---
OS: ---
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: smeserver-fail2ban
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
Target Milestone: ---
The template for /etc/jail.conf for nextcloud has a legacy filter entry for
owncloud. This creates an error preventing fail2ban from starting.
Installed version:
[root@fwbox jail.conf]# cat 30Service55nextcloud
[nextcloud]
enabled = true
filter = owncloud
action = smeserver-iptables[port="$port",protocol=tcp,bantime=$bantime]
logpath = /home/e-smith/files/nextcloud/data/nextcloud.log
maxretry = 3
port = 80,443
protocol = tcp
should be
[root@fwbox jail.conf]# cat 30Service55nextcloud
[nextcloud]
enabled = true
filter = nextcloud
action = smeserver-iptables[port="$port",protocol=tcp,bantime=$bantime]
logpath = /home/e-smith/files/nextcloud/data/nextcloud.log
maxretry = 3
port = 80,443
protocol = tcp
making this change then running
signal-event fail2ban-conf
and fail2ban starts as expected.
--
You are receiving this mail because:
You are the QA Contact for the bug._______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/
