Login attempt protection limits failed password attempts per account and per connection. Restrictions expire on their own, and existing signed-in sessions are never blocked.
Where to find it: ARN SiteWatch → Access Security → Login Protection.

How the limits work
- Account limit. Failed attempts for the same account are counted together, whether someone types the username or the email address.
- Connection limit. Failed attempts from the same connection address are counted separately, across all accounts.
- Attempt window. A restriction lasts for the attempt window and then expires automatically.
- A successful login clears the account's counter. Failures from a connection address remain recorded.
SiteWatch counts the visitor address: by default the address of the server connection, with each IPv6 /64 network counted as one visitor. Behind a reverse proxy or CDN, that address belongs to the proxy, so all visitors would share one counter and one limit could affect many legitimate visitors. (SiteWatch 2.1.0 and later) Name the addresses of your proxy or CDN and the header it sets under Site Protection → Requests & Endpoints → Visitor address behind a proxy or CDN; see Request patterns, endpoint limits and early protection. SiteWatch then reads the visitor from that header only when the connection comes from those addresses. Forwarded headers from any other source are never trusted.
Turn on login attempt protection
| Setting | Default | Allowed range |
|---|---|---|
| Account failure limit | 8 | 3 to 50 |
| Connection failure limit | 30 | 10 to 200 |
| Attempt window (minutes) | 15 | 5 to 60 |
- Open Access Security → Login Protection.
- Tick Enable login attempt protection.
- Review the limits in the table above and change them if your site needs it.
- Click Save login protection.
- Test a normal login in another browser while you keep your current administrator session open.
Every setup profile turns this protection on with the current values. See Complete the security setup.
Clear login counters
If a legitimate user is locked out, an administrator who is still signed in can click Clear login counters under Administrator recovery. All counters are removed and the restriction ends immediately.
Recover access with hosting help
If every administrator is locked out, wait for the attempt window to pass, or ask your host to run this WP-CLI command as the hosting account of the WordPress installation:
wp option delete sitewatch_login_settings
It turns off the login limits without removing reports. SiteWatch never creates a public bypass link or a shared recovery password.
Note: A lockout can also come from other policies: a required authenticator, a pending account approval or browser verification. See FAQ about sign-in, approvals and plugin reviews.