Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

custom jails and filter not loaded #53

Closed
MPatzek opened this issue Jul 22, 2020 · 0 comments
Closed

custom jails and filter not loaded #53

MPatzek opened this issue Jul 22, 2020 · 0 comments

Comments

@MPatzek
Copy link

MPatzek commented Jul 22, 2020

Hey,
maybe I am too dumb, but I am trying to run this fail2ban images with nextcloud using docker-compose. I use the following folder structure:
nextcloud/app

  • nextcloud folder with the log
    nextcloud/fail2ban
    -- filter.d
    **** nextcloud.conf
    -- jail.d
    **** jail.conf

The part of my docker-compsoe file:
fail2ban: image: crazymax/fail2ban:latest container_name: nextcloud-fail2ban networks: - nextcloud_network cap_add: - NET_ADMIN - NET_RAW volumes: - nextcloud/fail2ban:/data - nextcloud/app/data:/var/log:ro env_file: - ./fail2ban.env restart: unless-stopped

wenn running the compose I see the following log:
Setting timezone to Europe/Berlin... Setting SSMTP configuration... WARNING: SSMTP_HOST must be defined if you want fail2ban to send emails Initializing files and folders... Setting Fail2ban configuration... Checking for custom actions in /data/action.d... Checking for custom filters in /data/filter.d... 2020-07-22 15:28:15,557 fail2ban.configreader [1]: INFO Loading configs for fail2ban under /etc/fail2ban 2020-07-22 15:28:15,558 fail2ban.configparserin [1]: INFO Loading files: ['/etc/fail2ban/fail2ban.conf'] 2020-07-22 15:28:15,559 fail2ban.configparserin [1]: INFO Loading files: ['/etc/fail2ban/fail2ban.conf'] 2020-07-22 15:28:15,560 fail2ban [1]: INFO Using socket file /var/run/fail2ban/fail2ban.sock 2020-07-22 15:28:15,560 fail2ban [1]: INFO Using pid file /var/run/fail2ban/fail2ban.pid, [INFO] logging to STDOUT 2020-07-22 15:28:15,563 fail2ban.configreader [1]: INFO Loading configs for jail under /etc/fail2ban 2020-07-22 15:28:15,564 fail2ban.configparserin [1]: INFO Loading files: ['/etc/fail2ban/jail.conf'] 2020-07-22 15:28:15,579 fail2ban.configparserin [1]: INFO Loading files: ['/etc/fail2ban/paths-debian.conf'] 2020-07-22 15:28:15,580 fail2ban.configparserin [1]: INFO Loading files: ['/etc/fail2ban/paths-common.conf'] 2020-07-22 15:28:15,582 fail2ban.configparserin [1]: INFO Loading files: ['/etc/fail2ban/paths-overrides.local'] 2020-07-22 15:28:15,583 fail2ban.configparserin [1]: INFO Loading files: ['/etc/fail2ban/paths-common.conf', '/etc/fail2ban/paths-debian.conf', '/etc/fail2ban/jail.conf'] 2020-07-22 15:28:15,628 fail2ban.server [1]: INFO -------------------------------------------------- 2020-07-22 15:28:15,629 fail2ban.server [1]: INFO Starting Fail2ban v0.11.1 2020-07-22 15:28:15,630 fail2ban.observer [1]: INFO Observer start... 2020-07-22 15:28:15,637 fail2ban.database [1]: INFO Connected to fail2ban persistent database '/data/db/fail2ban.sqlite3' Server ready

Executing docker exec -t nextcloud-fail2ban fail2ban-client status results in
Status |- Number of jail: 0 - Jail list:
`

Is my path configuration wrong? Or where is my mistake?

with best regards

@MPatzek MPatzek closed this as completed Jul 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant