How to set up brute force protection for panel logins

For server administrators · Updated 2026-10-29

On this page
  1. Steps
  2. What gets blocked
  3. The lists on the page
  4. Good to know
  5. Common questions

Brute force protection counts failed logins to the admin panel, the control panel and the API, and blocks an address that fails too often. It is always on; you choose how strict it is.

Steps

  1. In the administrator panel (https://<server>:2087), open Brute Force Protection (section Security).
  2. Under Settings, set:
    • Max failures — failed logins allowed per address (default 5, from 1 to 100).
    • Window (min) — the period they are counted in (default 15 minutes, up to 1440).
    • Block for (min) — how long the address is blocked (default 15 minutes, up to 10080 = 7 days).
    • Whitelisted IPs (comma separated) — addresses that are never blocked, for example 203.0.113.10, 198.51.100.25. Single addresses only, no ranges.
  3. Click Save.

What gets blocked

  • An address with Max failures failed logins within Window (min) is blocked for Block for (min). It sees "Too many failed login attempts. Your IP is temporarily blocked."
  • An IPv6 address is counted and blocked together with its whole /64 network.
  • An account under attack from many addresses: when one username gets 3 × Max failures failed logins (at least 10) within the window, its login is paused for everyone: "Too many failed login attempts for this account. Please try again in a few minutes."
  • Wrong two-factor codes and wrong API tokens count as failed logins too.
  • At the firewall too: with Block brute-force attackers at the firewall (all services), not only at the login page ticked on the Firewall page (on by default), the address is also blocked for every service for the same time.

The lists on the page

  • Blocked IPs — address, reason (number of failures and the last username tried), until when, and Unblock.
  • Recent failed logins — the last 50 failures with time, address and username.

Good to know

  • Whitelisted IPs here protect against the login block only. To keep an address out of every firewall block, also add it with Always allow on the Firewall page.
  • SSH, email and FTP logins are protected separately by fail2ban. See fail2ban bans.
  • Website logins (WordPress and similar) are protected by the Protection Shield.

Common questions

A customer is blocked. How do I free them?

Click Unblock next to their address under Blocked IPs. See how to unblock an IP address.

Should I make the limits stricter?

The defaults stop password guessing while giving people a few tries. Add two-factor authentication for real protection: a guessed password alone is then not enough.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.