1_We will be very grateful, if your problem was described as completely as possible,
2enclosing excerpts from logs (if possible within DEBUG mode, if no errors evident
3within INFO mode), and configuration in particular of effected relevant settings
4(e.g., with ` fail2ban-client -d | grep 'affected-jail-name' ` for a particular
5jail troubleshooting).
6Thank you in advance for the details, because such issues like "It does not work"
7alone could not help to resolve anything!
8Thanks! (remove this paragraph and other comments upon reading)_
9
10### Environment:
11
12_Fill out and check (`[x]`) the boxes which apply. If your Fail2Ban version is outdated,
13and you can't verify that the issue persists in the recent release, better seek support
14from the distribution you obtained Fail2Ban from_
15
16- Fail2Ban version (including any possible distribution suffixes):
17- OS, including release name/version:
18- [ ] Fail2Ban installed via OS/distribution mechanisms
19- [ ] You have not applied any additional foreign patches to the codebase
20- [ ] Some customizations were done to the configuration (provide details below is so)
21
22### The issue:
23
24_Summary here_
25
26#### Steps to reproduce
27
28#### Expected behavior
29
30#### Observed behavior
31
32#### Any additional information
33
34### Configuration, dump and another helpful excerpts
35
36#### Any customizations done to /etc/fail2ban/ configuration
37```
38```
39
40#### Relevant parts of /var/log/fail2ban.log file:
41_preferably obtained while running fail2ban with `loglevel = 4`_
42
43```
44```
45
46#### Relevant lines from monitored log files in question:
47
48```
49```