Hi @vaniivan,
Are you seeing blocks reported in Live Traffic when this plugin attempts to auth? Usually, expanding these entries by clicking them will either let you add the requests to Wordfence’s allowlist via a button, or at least explain why they’re being blocked – usually a firewall rule or a custom Brute Force/Rate Limiting setting.
If you’re unable to find a way around it, also try again while Learning Mode is enabled.
From the Wordfence Dashboard click on Manage WAF. Then you will see Basic Firewall Options > Web Application Firewall Status. Change the option to Learning Mode. Now perform the actions that were causing issues. This will help Wordfence learn that these actions are normal and it will allow them in the future. After you have finished performing the actions, switch the WAF from Learning Mode back to Enabled and Protecting. Now test to see if these actions work correctly.
Let me know how that goes,
Peter.
Hi, thanks for the tips. WordFence in this case reports “attempted a failed login as “username””, even though that same login data (sent as Basic auth header in both cases) is working immediately after disabling WordFence plugin.
-
This reply was modified 3 years, 6 months ago by
vaniivan.
-
This reply was modified 3 years, 6 months ago by
vaniivan.
It stems from Recaptcha login protection. When I set the Recaptcha to test mode, the basic auth starts working.