Bit51 (part of the iThemes family)
Forum Replies Created
-
Thanks for the feedback. I will use it in helping with some usability improvements (as I developed this plugin for my own use I’ve never had much feedback in this area).
@voidzero I like the generic suggestions idea and have posted it as sticky.
@bigwhitedog what is the issue with Windows Servers?
Not a bad idea. I’ll look at adding regex support in future versions as well as a more intuitive list in general.
I’ll take a look back at user agent, I use it quite a bit with success….
…I can also add a field for remote host. I’ll add that to upcoming versions.
Sounds like a 404 lockout. Check the logs in the backend and see if you’re getting a bunch of 404 errors. Then you have 3 options…
….Fix the 404 errors
….Increase the lockout threashold
….Disable 404 Intrusion detection@kovazg Glad it works. This makes me think I’ll include a checker for the cache in the future.
@sabirtiger Did you allow it to change core files?
In most cases it is the “Filter Suspicious Query Strings” option in System Tweaks that is causing the error. Try changing the System Tweaks settings and please report back if you can find the conflicting feature.
It could be something failed when updating the database. Are you using any special roles or anything else non-standard in regards to the user?
The plugin’s lockouts would just display ‘error’ so that isn’t what’s logging you out. Check your php logs. I’m guessing this is actually a memory error.
Try clearing the BWPS htaccess rules as most migration plugins will not fix them. Also check your wp-config and make sure all paths are correct. If those are both right I would suggest looking at other plugins or the migration itself as it something may have become corrupted.
What two lines are you referring to and what is the error message it is giving you?
You definitely don’t want to run setup again. This is an odd one. This typically happens when WordPress can’t find the wp-config file.
Is there something in your file that could be causing the redirect? Perhaps a location statement?
In all honesty that is a rule I am still tuning and was created in the port from Apache to NGINX. I will take a closer look but it is basically looking for this specific parameters and then blocking accordingly.