Skip to content

Brute Force Protection

DirectiveSyntaxDefault
BruteForceProtectionOn|OffOff
BruteForceAllowedAttemptsN10
BruteForceWindowseconds300
BruteForceActionblock|throttle|logblock
BruteForceThrottleDurationmilliseconds5000
BruteForceXForwardedForOn|OffOff
BruteForceTrustedProxyIP/CIDR [IP/CIDR ...](none)
BruteForceWhitelistIP/CIDR [IP/CIDR ...](none)
BruteForceProtectPath/path(none)
LSBruteForceProtection On
LSBruteForceAllowedAttempts 5
LSBruteForceWindow 600
LSBruteForceAction throttle
LSBruteForceThrottleDuration 10000
LSBruteForceXForwardedFor On
LSBruteForceTrustedProxy 10.0.0.0/8
LSBruteForceWhitelist 192.168.1.0/24 10.0.0.0/8
LSBruteForceProtectPath /wp-login.php

This throttles login attempts to 5 per 10 minutes, with a 10-second delay between throttled requests. Requests from the whitelisted subnets are exempt. Because BruteForceTrustedProxy is set, X-Forwarded-For is trusted only when the request arrives via 10.0.0.0/8.

When the firewall daemon is running, a threshold crossing also escalates to an nftables kernel drop — the attacker’s packets are discarded before reaching OpenLiteSpeed at all. The notification fires exactly once per attacker per window; the block carries the window as its TTL and expires automatically. Without the daemon, the 403 above is the complete behaviour.