dwinden
Forum Replies Created
-
@marcel Jong
Glad to hear that the issue is resolved.
Note that since the iTSec plugin is a subset of the iTSec Pro plugin everything I said in my previous post also applies to the Pro plugin.
So as this issue seems to be solved please mark this topic as ‘resolved’.
dwinden
@marcel Jong
Could be you have forgotten about Away Mode.
If the file wp-content/uploads/ithemes-security/itsec_away.confg exists delete it. Then retry.Note that iThemes removed a rather important feature (Security Status) as of the 5.2.0 release. This release also introduced many bugs. Some of those bugs got fixed in the subsequent 5.2.1 bugfix release while many others remained. Also note that where iThemes normally adds a post to their blog announcing a new iTSec release they wisely kept quiet this time …
Best option is to download the previous (5.1.1) release and stick with that till iThemes fires up their marketing machine again, announcing the latest & greatest iTSec release blah blah blah …
dwinden
Ok, try and disable the Enable HackRepair.com’s blacklist feature setting in the Banned Users section of the iTSec plugin Settings page.
I haven’t seen ‘RavenCrawler’ in the list but who knows …
dwinden
Ok, I see.
It’s probably something in the .htaccess file that is blocking it.
Reactivate the iTSec plugin (if not already).And then if possible please post the content of the .htaccess file while obfuscating any sensitive info.
Also confirm you are using the iTSec plugin release 5.2.1
dwinden
What makes you think it is the iTSec plugin stopping RavenCrawler ?
Does it work when you temporarily deactivate the iTSec plugin ?dwinden
It’s a bit weird because the Ban Hosts CIDR type entry validation code accepts the full range from /1 to /32 as valid values.
But indeed it looks like when converting those CIDR values to .htaccess entries only /8, /16, /24 and /32 values are converted.
So there is clearly a mismatch between CIDR entry validation and .htaccess CIDR range conversion.
dwinden
@wp Monkey
If this is still an issue why don’t you simply create a new user and then delete the old user account (while transferring any existing content to the new user) ?
It seems the user account got corrupted in a way that the iTSec plugin cannot work with it.
dwinden
@srd75 (Steve)
Yes. Security -> Settings -> WordPress Tweaks -> Disable login error messages
If the info above answers your question please mark this topic as ‘resolved’.
dwinden
This way for sure this topic is not moving forward …
Find the common denominator (there are 3 posters in this topic) and once the cause is found think about a solution.
Perhaps you are all three using a caching plugin …Meanwhile as a workaround (and perhaps method towards finding the cause) disable the Write to Files setting in the Global Settings section on the iTSec plugin Settings page.
Then everytime after making changes to certain settings manually copy\paste the plugin rules from the Rewrite Rules section on the iTSec plugin Dashboard page to the .htaccess file.
Please note that only changing certain specific settings affects the Rewrite Rules.
dwinden