PD Guard can add alerts and a configurable block duration to the failed-admin-login evidence it reads from WHMCS. This is separate from successful sign-in alerts and the Pro Admin Access Lock.

Review the intended policy

1. Open PD Modules → Guard → Settings.
2. Review Alert + extend lockout on failed admin logins.
3. Set Failed attempts before alert / lockout within its supported range of 1–3.
4. Review Block duration (minutes), which accepts 5–1,440 minutes.
5. Choose Save settings and check Failed-login alerting in the PD Modules jobs view.

The job is registered at a five-minute interval and needs the platform cron. It is not an inline alert for every mistyped password. A lower threshold can treat ordinary mistakes as an episode. Do not deliberately fail production sign-ins to test it.

Check an observed episode

Compare the relevant job time, existing ban, recorded failed-login evidence and the module’s Activity information. PD Guard reads both recognised current failed-login bans and the platform’s unexpired failure tracker. Evidence that has already expired or disappeared may not be visible to the next job.

When an episode qualifies, the block lasts at least the intended duration and preserves a later existing ban expiry. The module records the episode to avoid repeating it on every tick. A failed notification does not mean that the block was never applied, and the recorded episode is not a persistent mail-retry queue.

Resolve access without blind retries

Use the normal WHMCS administration and recovery process to review an unexpected ban. Do not change security controls repeatedly or run internal database repairs. Keep the redacted episode/job times, settings and exact error for an unexplained module result.

See the PD Guard WHMCS guide for related tasks, or explore PD Guard.