Automatically closed - issue fixed for 2 weeks with no activity.
Although Autoban integrates with Advban, and Advban enables expiry of banned IPs, this may not work as expected. On every cron run, Autoban just bans the IP again. This occurs because the dblog entries that cause the ban may persist for some time - months perhaps depending on how many entries the dblog is configured to store and how often entries are added.
For example, take this scenario:
So even though we are using Advban to ensure IPs are not permanently banned (as they may be dynamic IPs re-assigned to innocent users), and we set bans to expire after 24 hours, Autoban will continually re-ban the IP potentially for a much longer period depending on how long log entries causing the ban persist in the dblog.
A potential solution is to make Autoban rules configurable so that they are only applied to a limited time window of log entries.
Taking the example above where an IP is banned and the ban expires after 24 hours, if Autoban rules are configured to only look at the most recent log entries occurring in the last 24 hours, then the IP will not be re-banned after the ban has expired (assuming the IP has stopped generating log entries that caused the IP ban in the first place).
Patch for 8.x-1.7 version to follow ...
Fixed
1.7
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Automatically closed - issue fixed for 2 weeks with no activity.