Fail2Ban doesn't work on NC with NCP 1.18.0

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
1

Hi,

I´ve managed to successfully install NCP 1.18.0 on my Raspberry Pi 4 4GB.
After completing the configuration and some testing the system is almost working perfectly.

Only fail2ban seems not to work correct after login in with wrong
passwords on Nextcloud. It is configured to block failed logins after three attempts.

I checked the nextcloud.log logfile on /var/www/nextcloud/data/ and can confirm
that it logs everything as it should be, but fail2ban cannot recognize it as it seems.
At least it works for the ssh-service tough.

If I try to check it with the command “fail2ban-client status nextcloud” it shows:

Status for the jail: nextcloud
|- Filter
| |- Currently failed: 0
| |- Total failed: 0
| - File list: /var/www/nextcloud/data/nextcloud.log - Actions
|- Currently banned: 0
|- Total banned: 0
`- Banned IP list:

Can anyone tell me what the problem could be? Could this be an issue with
permissions?

I want to add that I currently running the /boot partition on the sd-card while
having the system running completely on a SSD drive for performance reasons.

Thanks in advance.
mraton

2

I want to add that the command “fail2ban-regex /path/to/log /path/to/filter” shows
the amount of login attempts by me as missed lines.

So it can read the log file but cannot interpret the logentries as it seems.

3

If your ncdata has been moved, so has your nextcloud.log
Edit /etc/fail2ban/jail.local so it knows where the log is.
Example /media/ncdata/nextcloud.log

4

Same problem for me. SSH works, NC not. The Path is correct in the jail.local

5

I was unable to solve the problem. So I decided to install Nextcloud with Fail2Ban manualy.

So far everything is going as it should.

Greetings.

6

Still problem with newest ncp version.

7

Bug reported on Github