view mod_log_auth/README.md @ 6514:668b1f0a4dc6

mod_c2s_limit_sessions: Fix check when it's the first connection Creation of the sessions[username] entry happens after the "pre-resource-bind" event, before the "resource-bind" event. Thus, for a users first connection, it may not exist. This led to an 'attempt to index a nil value' error, fixed here.
author Kim Alvefur <zash@zash.se>
date Wed, 08 Apr 2026 15:56:38 +0200
parents 24cc4b04d078
children
line wrap: on
line source

---
labels:
- 'Stage-Stable'
summary: Log failed authentication attempts with their IP address
...

Introduction
============

Prosody doesn't write IP addresses to its log file by default for
privacy reasons (unless debug logging is enabled).

This module enables logging of the IP address in a failed authentication
attempt so that those trying to break into accounts for example can be
blocked.

fail2ban configuration
======================

fail2ban is a utility for monitoring log files and automatically
blocking "bad" IP addresses at the firewall level.

With this module enabled in Prosody you can use the following example
configuration for fail2ban:

    # /etc/fail2ban/filter.d/prosody-auth.conf
    # Fail2Ban configuration file for prosody authentication
    [Definition]
    failregex = Failed authentication attempt \(not-authorized\) for user .* from IP: <HOST>
    ignoreregex =

And at the appropriate place (usually the bottom) of
/etc/fail2ban/jail.conf add these lines:

    [prosody]
    enabled = true
    port    = 5222
    filter  = prosody-auth
    logpath = /var/log/prosody/prosody*.log
    maxretry = 6

Compatibility
-------------

  ------- --------------------
  trunk   Works as of 26-03-15
  13.x    Works
  0.12    Works
  ------- --------------------