Ok, I just completed a quick test and …
Away Mode works exactly as I thought it does.
You need to distinguish between manual login attempts:
– A human accessing the WP Dashboard page (= wp-login.php GET request) and then entering the username and password followed by clicking on the blue Login button (= wp-login.php POST request).
and automated login attempts:
– Most brute force login attempts are automated. They skip the wp-login.php GET request and do a direct wp-login.php POST request…
Away Mode is designed to only redirect wp-login.php GET requests…
So Away Mode is only effective against manual login attempts.
The wp-login.php GET request is redirected using the WP get_option(‘siteurl’) function (= WordPress Address(URL) field in General Settings). The iTSec plugin Logs page will show a new entry named Away Mode Triggered for every attempt (GET request) to access the WP Dashboard login page.
I noticed you seem to be getting a 404 page. Check your WordPress Address(URL) field in General Settings and try and access its current value to see whether that url returns a 404. It could be there is a bug in Away Mode where it should be redirecting to Site Address(URL) using the get_option(‘home’) function…
Note this is only relevant in WordPress installs where the WordPress Address(URL) is not equal to the Site Address(URL)…
Another explanation could be that you have enabled the iTSec plugin Hide Backend feature. Once this feature is enabled you can no longer access the wp-login.php file directly. It will return a … 404.
An automated brute force login attempt passes the username and password field values programmatically using a wp-login.php POST request. Even though Away Mode is triggered it ALSO continues with attempting to log in …
(Technically speaking there is no exit performed after the Away Mode redirect …)
There will be just as much Away Mode Triggered entries in the Logs page as there are Invalid Login Attempt and Host or User Lockout entries …
So Away Mode will not prevent your site from being hammered by automated login attempts as generated by brute force attacks …
It will only protect your site from accessing the WP Dashboard login page and thus manual (human) login attempts …
dwinden