You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have iThemes Security plugin installed and after several wrong attempts some IPs made it to a blacklist and are banned permanentely.
Strangely enough I’m still getting these IP’s attempts logged as “N/A user logged-out”.
This is the portion of the code, iThemes Security added to .htaccess:
<IfModule mod_authz_core.c>
<RequireAll>
Require all granted
Require not env DenyAccess
Require not ip 91.210.145.165
</RequireAll>
</IfModule>
<IfModule !mod_authz_core.c>
Order allow,deny
Allow from all
Deny from env=DenyAccess
Deny from 91.210.145.165
</IfModule>
91.210.145.165 is the IP that is keeping to be logged by your plugin.
This issue is not the same as #125 - in that case it's logging attempts which weren't blocked (before the evaluating the password as wrong) and this is a correct behaviour. In my case it is logging attemts which shouldn't happended at all.
Or does it mean, that the iThemes actually isn't blocking those IPs? BTW there are no attemps for 91.210.145.165 in iTheme's own log after the user was banned.
The text was updated successfully, but these errors were encountered:
I have iThemes Security plugin installed and after several wrong attempts some IPs made it to a blacklist and are banned permanentely.
Strangely enough I’m still getting these IP’s attempts logged as “N/A user logged-out”.
This is the portion of the code, iThemes Security added to .htaccess:
91.210.145.165 is the IP that is keeping to be logged by your plugin.
This issue is not the same as #125 - in that case it's logging attempts which weren't blocked (before the evaluating the password as wrong) and this is a correct behaviour. In my case it is logging attemts which shouldn't happended at all.
Or does it mean, that the iThemes actually isn't blocking those IPs? BTW there are no attemps for 91.210.145.165 in iTheme's own log after the user was banned.
The text was updated successfully, but these errors were encountered: