How to stop WordPress login attacks (brute force) on all sites

For server administrators · Updated 2026-10-29

On this page
  1. Steps
  2. What counts as a failed login
  3. What happens to a blocked address
  4. Good to know
  5. Common questions

Bots try thousands of passwords on WordPress, Joomla and Drupal logins. The Protection Shield counts failed logins per address across all websites on the server and blocks an address that goes over the limit. It is on by default.

Steps

  1. In the administrator panel (https://<server>:2087), open Protection Shield (section Security).
  2. Under Login protection, tick Block addresses that guess passwords on WordPress, Joomla, Drupal….
  3. Failed logins per minute (all sites) — how many failed logins one address may make per minute, added up over all sites. Default 20, from 5 to 500.
  4. Block for (minutes) — how long the address is blocked. Default 60, from 10 minutes to 7 days (10080).
  5. Click Save.

What counts as a failed login

  • A POST to wp-login.php that does not log in.
  • Any POST to xmlrpc.php (WordPress), administrator/index.php (Joomla) or user/login (Drupal).

The shield reads the logs about once a minute, so a block starts within about a minute of the attack.

What happens to a blocked address

  • It is blocked in the server firewall for every service, for Block for (minutes).
  • If it comes back within a day, it is blocked for 24 hours.
  • It shows under Blocked now with the time the block ends, and as Password guessing in Recent events.
  • Never blocked: this server, addresses on the Firewall allow list and anyone who signed in to the panel in the last day.

Good to know

  • Lower the limit (for example to 10) if attacks spread over many sites still get through; raise it if a busy site with many real logins gets its visitors blocked.
  • Apps that use xmlrpc.php (for example a mobile app or a publishing tool) send POST requests that count. If such a user is blocked, add their address to the allow list in Firewall.
  • Customers see the blocks on their sites in Access Control in their control panel.

Common questions

I blocked myself while testing. How do I get back in?

Sign in to the admin panel from another connection and click Unblock under Blocked now. Addresses that signed in to the panel in the last day are never blocked, so this rarely happens to administrators.

Does this protect the control panel login too?

No. Logins to the admin panel, control panel and API are protected by Brute Force Protection. See brute force protection.

Was this article helpful?

Still stuck?

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