How to set up brute force protection for panel logins
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
- In the administrator panel (
https://<server>:2087), open Brute Force Protection (section Security). - 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
15minutes, up to 1440). - Block for (min) — how long the address is blocked (default
15minutes, 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.
- Max failures — failed logins allowed per address (default
- 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
/64network. - 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.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- How to unblock an IP address (customer can't connect)
A customer or you cannot reach the server or log in: find which protection blocked the IP address and unblock it in the right place in the admin panel.
- How to restrict the admin panel to your IP addresses
Allow only your own IP addresses or ranges to open the admin panel on port 2087, and how to get back in with one command if you lock yourself out.
- How to enable two-factor authentication (2FA) for your login
Protect your admin panel or control panel login with a 6-digit code from an authenticator app, save your 10 recovery codes, and sign in with 2FA.
- SSH and email login bans (fail2ban): view and unban
How fail2ban bans addresses after failed SSH, IMAP, POP3, SMTP and FTP logins, the ban limits, and how to see and lift bans in the admin panel.