A simple and clean web-based reporting tool for Fail2Ban events.
Turn your daily Fail2Ban logs into searchable and filterable JSON reports – right on your webspace.

📦 Features

Parses fail2ban.log into daily JSON logs
Filter by date, action (Ban / Unban), jail and IP fragment
Responsive dark-themed UI
Easy to deploy, no database, no frameworks
The JSON output is plain and lightweight. You can post-process or archive old data easily.
This tool requires no database and can run even on very minimal webspace setups. (e.g. RaspberryPi)

🛡️ This tool does not replace proper intrusion detection and access control. It is a visualization layer and should be deployed accordingly.

Screenshot

📝 Version-Notes

Better Structure

Stylesheet have been moved to /assets/css/style.css for easy customization.
Javascripts mooved to /assets/js/
Screenshot for GitHub Readme mooved to /assets/images/ => I can remove that later with an automated Setup
Action Button added for later Actions like "Ban IP"
improved .htaccess File

File Structure

/
├── index.php               # Main web frontend (PHP + HTML)
├── .htaccess               # Basic web server protection and security headers
├── LICENSE                 # License file (GPLv3)
├── README.md               # Project documentation and setup instructions
├── fail2ban_log2json.sh    # Bash script to convert Fail2Ban logs to JSON
├── assets/
│   ├── css/
│   │   └── style.css       # Main stylesheet for the Fail2Ban report UI
│   ├── js/
│   │   ├── jsonreader.js   # Core JavaScript: loads and renders JSON data
│   │   └── action.js       # Handles action button events (e.g. Ban IP)
│   └── images/
│       └── Fail2Ban.png    # Screenshot for GitHub Readme
└── includes/
    └── list-files.php      # PHP script to list and prepare JSON files for frontend

Files List

.htaccess
Basic web server protection and security headers to restrict access to sensitive files and improve security.
Fail2Ban.png
Screenshot or logo image related to the Fail2Ban Report project.
LICENSE
License file specifying the usage terms of the project (GPLv3).
README.md
Project documentation including setup instructions, features, and roadmap.
fail2ban_log2json.sh
Bash script that parses Fail2Ban logs and converts them into daily JSON files for easy web-based reporting.
index.php
Main web frontend file combining PHP and HTML to display the report interface and load JSON data dynamically.
assets/
Directory containing static assets such as CSS, JavaScript, and images.
- assets/css/style.css
  Stylesheet defining the appearance and layout of the Fail2Ban report web interface.
- assets/js/jsonreader.js
  JavaScript responsible for fetching JSON data and rendering the report table with filters.
- assets/js/action.js
  JavaScript handling user interactions with action buttons, such as "Ban IP".
- assets/images/Fail2Ban.png
  Screenshot for Github Readme.
includes/
Directory containing PHP include files.
- includes/list-files.php
  PHP script to scan the archive directory, list available JSON log files, and prepare data for the frontend.

⚙️ Setup Instructions

1️⃣ Bash Script Setup (`fail2ban_log2json.sh`)

Save the script fail2ban_log2json.sh anywhere on your server (e.g. /usr/local/bin/).
Make it executable:
```
chmod +x /path/to/fail2ban_log2json.sh
```
Open the script and adjust the following lines to fit your environment: LOGFILE="/var/log/fail2ban.log" # path to your Fail2Ban log OUTPUT_JSON_DIR="/var/www/Fail2Ban/archive" # output directory for .json files (served by webserver)
Run the script manually or via a daily cronjob: Run script via
```
./fail2ban_log2json.sh
```
or run it via cronjob:
```
crontab -e
```
then
```
@daily /path/to/fail2ban_log2json.sh
```
or any other time that fits your needs (you can try the crontab time generator on https://suble.net/cronhelper/ (⚠️german language)

2️⃣ Web Interface Setup (Webspace)

On your webserver, create a folder for the tool (e.g. Fail2Ban)
```
/var/www/html/Fail2Ban/
```
Place the following files inside this folder:
- index.php
- style.css
- .htaccess
Inside the same folder, create a subfolder named archive:
```
/var/www/html/Fail2Ban/archive/
```
Make sure the webserver (e.g. www-data) has read access to this directory and write access if you want to store JSON files directly there.
```
chown -R www-data:www-data /var/www/html/Fail2Ban/*
```

🖥️ Usage

After the first log run is processed, open your browser and go to:

   https://yourdomain.tld/Fail2Ban/

You will see a dropdown to choose the date, filter by action, jail, and IP.

Protecting Your Fail2Ban Report with .htaccess

To enhance the security of your Fail2Ban report, a .htaccess file is provided that:

Disables directory listings
Blocks direct access to sensitive files such as .json and .css
Sets basic HTTP security headers for safer browsing

How to Use the `.htaccess` File

Save the provided .htaccess file in the root directory of your Fail2Ban report (where index.php resides).
Ensure your web server allows .htaccess overrides (typically via AllowOverride in Apache).
The .htaccess will automatically protect files in the main directory and subfolders like /archive/.

Important Security Notice

While this .htaccess provides a basic level of protection, it is highly recommended to implement additional security measures, such as:

HTTP authentication (Basic Auth) to restrict access to authorized users only
IP-based access restrictions to allow only trusted networks or addresses

Fail2Ban reports often contain sensitive security-related data. Adding these layers of protection will help prevent unauthorized access and keep your data safe.

For example, you can set up Basic Auth with:

AuthType Basic
AuthName "Restricted Area"
AuthUserFile /path/to/.htpasswd
Require valid-user

You can use the htpasswd helper for your htpasswd files (choose bcrypt as algorythm as it is better) on https://suble.net/htpasswd/ (⚠️ german language)

or restrict by IP:

Require ip 192.168.1.0/24
Require ip 203.0.113.5

📄 License

This project is released under the GPLv3 License. Feel free to modify and share.

🗺️ Roadmap

Fail2Ban-Report is designed to be lightweight, modular, and open to future improvements. The following features are currently planned:

⚙️ Setup & Automation

Setup script to automate initial installation, including directory structure and permissions
Optionally auto-configure a daily cronjob

🔐 Security Features

Integration of a stronger .htaccess file for basic access control and secure defaults

🔥 Active Defense Integration

Allow manual IP blocking directly from the interface via iptables or ufw
Optionally enable automatic blocking of suspicious IPs based on defined criteria

🧩 Open to Contributions

I'm happy to hear from users and contributors!
Whether it's:

feature requests,
improvement ideas,
or even pull requests —
Feel free to reach out or contribute directly.

If you use this tool and think "Hey, wouldn't it be cool if it could also do XYZ?" — I'm all ears!

README.md Unescape Escape

Fail2Ban-Report