dwinden
Forum Replies Created
-
Ah ok you are switching, right. I knew I was missing something …
So how exactly do you try to go back to admin ?
Using the browser back button or Dashboard menu option ?dwinden
I clicked on the ‘Přihlásit se’ link (first guess) on your website homepage and navigated straight to the WP Dashboard login screen…
Using Firefox 44 on Windows 7 Pro SP1.
dwinden
It could be the host lockouts are occurring because of too many 404 requests.
Did you enable the 404 Detection feature ?
If so please check the Logs page and select 404 Errors as the Select Filter:.If there are many 404 Errors logged you could temporarily try and disable the 404 Detection feature. Just too see whether is has any impact on this issue.
dwinden
Even though these are just notices I think its certainly worth the trouble to find out the exact origin and if possible fix them.
These notices do indicate aged code that no longer complies to the current WP release (4.4.1) standards.
I assume this is in a WP 4.4.1 env, right ?I don’t really expect solving these notices will have any impact on the blank page issue, but you never know …
It won’t hurt to fix these notices.Install and activate the oik-bwtrace plugin for tracing the exact origin of the obsolete notices.
dwinden
Ok, one thing is for sure this is not an iTSec plugin issue.
Also note ‘login’ is one of the 5 default WP Dashboard slugs while the other ones are:
– admin
– dashboard
– wp-admin
– wp-login.phpThe iTSec plugin will never redirect from wp-admin to login …
That simply does not make any sense.Also it seems you are using a customized login page. So check that code.
dwinden
Ok, I see.
I think the issue here is that because you can specify a folder for 404 Whitelist people think that all files in that folder will then not trigger a 404 log entry and not be counted towards a lockout.
However it seems to me this is not how it is designed to work.
As to your wp-content/cache/standard*.js and standard*.css example I think the .css will generate a 404 entry in the log but it will not be counted towards a lockout.
The same will happen to *.js files if you add such entry to the 404 Ignored Filetypes setting.
If you really need 404 whitelisted folders to work differently the best thing to do would be to submit a feature request here.
dwinden
Thank you for opening a seperate topic for this issue.
Did you try setting WP_DEBUG to true in the wp-config.php file ?
And did you check your web server error_log file for any errors ?
dwinden