Thanks for the clear report and for narrowing it down with WPMU DEV. I’ve traced it: 5.7.12 introduced per-visitor login keys that expire after 12 hours or three uses, and when a page cache or CDN serves the login page (or the key itself) from cache, the browser submits a key the server has already retired, which the plugin wrongly treated as a bot. 5.7.14 fixes that: a stale key now simply gets refreshed instead of blocking the login, and the key fetch bypasses caches. If you can, before updating, turn on “Log Blocked Login Attempts” and check the Log entry’s reason, and let me know whether Defender’s login masking is on and what caching or CDN the site uses, so I can confirm it matches. Thanks for your patience.
Zero Spam 5.7.14 is now available and includes the fix for this.
What was happening: when the login form’s verification key had expired or been used up (which a cached login page or a two-step login flow like Defender’s can cause), Zero Spam treated it the same as a forged key and showed “Your IP has been flagged”. In 5.7.14 a lapsed key is handled as a missing one, and a two-step login whose password step has already succeeded is let through to the second step.
Could you update and try logging in through Defender’s two-step flow again? If you still see the message, please reply with the Zero Spam version, whether a caching plugin or CDN is in front of the site, and the exact wording of the error, and I’ll dig in further.
And if the update sorts it out, I’d really appreciate a rating. It helps other people find the plugin: https://wordpress.org/support/plugin/zero-spam/reviews/#new-post
We’re still experiencing the login issue after the plugin update.
Sorry it’s still happening, and thanks for testing the update straight away. To pin it down I need a few specifics, since the same message can come from more than one check:
- Confirm the Zero Spam version shown on your Plugins screen is 5.7.14 (not 5.7.12 or 5.7.13).
- The exact wording of the error you see on the login screen.
- In Zero Spam → Log, find the entry for your failed login (turn on “Log Blocked Login Attempts” under Settings → Zero Spam → Login if it isn’t already, then try again), open its Details, and tell me what the “Failed” line says. That one word tells me which check blocked you.
- Whether your own IP address appears under Blocked IPs, or your country under Blocked Locations.
- Whether Defender’s login masking (custom login URL) is on, and whether a caching plugin or a CDN (Cloudflare, SiteGround, Hostinger, etc.) sits in front of the site.
- If you can, the Zero Spam system report: Settings → Zero Spam → Settings → “Copy system report”, pasted here or sent via the contact form on zerospam.org if you’d rather not post it publicly.
If you need to log in meanwhile, adding your own IP under Settings → Zero Spam → IP Whitelist will let you through without turning the login protection off for everyone.