You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First sorry if this issue is already known, I couldn't find it here so far.
Environment:
freshly install Debian Bookworm on a remote server.
Fail2Ban version : v1.0.2
OS, including release name/version : Latest Debian 12
Fail2Ban installed via OS/distribution mechanisms
You have not applied any additional foreign patches to the codebase
Some customizations were done to the configuration (provide details below is so)
The issue:
Hi, on a just freshly installed Debian Bookworm I had this issue with fail2ban. Restarting it, rebooting or reinstallation didn't help. I had to manually change the backend from auto to systemd and then it worked.
Steps to reproduce
install debian bookworm, install ufw and fail2ban. Enable and start fail2ban.
Expected behavior
Fail2ban directly starts and filtering sshd.
Observed behavior
Fail2ban can't be started until manually change the backend from auto to systemd
Any additional information
Configuration, dump and another helpful excerpts
Any customizations done to /etc/fail2ban/ configuration
No customization was done on fail2ban configs.
Relevant parts of /var/log/fail2ban.log file:
fail2ban.configreader [2192]: WARNING 'allowipv6' not defined in 'Definition'. Using default one: 'auto'
fail2ban [2192]: ERROR Failed during configuration: Have not found any log file for sshd jail
fail2ban [2192]: ERROR Async configuration of server failed
Relevant lines from monitored log files:
The text was updated successfully, but these errors were encountered:
First sorry if this issue is already known, I couldn't find it here so far.
Environment:
freshly install Debian Bookworm on a remote server.
The issue:
Hi, on a just freshly installed Debian Bookworm I had this issue with fail2ban. Restarting it, rebooting or reinstallation didn't help. I had to manually change the backend from auto to systemd and then it worked.
Steps to reproduce
install debian bookworm, install ufw and fail2ban. Enable and start fail2ban.
Expected behavior
Fail2ban directly starts and filtering sshd.
Observed behavior
Fail2ban can't be started until manually change the backend from auto to systemd
Any additional information
Configuration, dump and another helpful excerpts
Any customizations done to /etc/fail2ban/ configuration
No customization was done on fail2ban configs.
Relevant parts of /var/log/fail2ban.log file:
Relevant lines from monitored log files:
The text was updated successfully, but these errors were encountered: