Bit51 (part of the iThemes family)
Forum Replies Created
-
I’ll look into the issue. Are you using a plugin to protect individual pages and posts?
That’s a new one. Are you using any kind of opcode or database query caching?
I will look at adding a whitelist feature in future versions.
I’m afraid I’m not familiar with pretty much any of those and therefore can only suggest you follow standard WordPress troubleshooting of shutting off all plugins and reactivating one at a time to confirm which is causing the issue.
Not sure this is a bug in the plugin itself however I do realize that changes the plugin make do make trigger the manifestation of the bug. I’ve seen this in numerous other situations however….
The “error” message actually means the plugin is doing it’s job. It is locking out the host most likely due to too many 404 errors. This means you have 2 options….
1.) Cleanup the 404s thereby stopping the lockouts and improving SEO
or
2.) Turn off the 404 intrusion detection on the “Intrusion Detection” screen.Thank you for the report. I had thought this fixed a few issues back (hadn’t heard about it since). I’ll take a look again and see if I can make the login work a little better.
As for a quick way to fix…
…What I’ve done in these situations is create a dump of the database, do a search replace, and re-upload the dump as the curent database. You’ll be down for a couple of minutes but it has worked for me (just keep the original dump in case anything is corrupted so that you can restore.).
The rules for Apache or NGINX are found in the “Dashboard” page.
Hi Coldad,
I know what you mean. I had a pro account with them but eventually had to get rid of them entirely due to 403 errors, numerous 404 errors, and a site slower than I had without it.
This depends on what you turned on. There are settings in your options table in your database, 2 tables of it’s own, a section it can write to .htaccess, and information it can write to wp-config.php. Note that in wp-config.php just changing items back to default such as the database prefix of if you moved wp-content it could really cause you some problems.
Thatnks pmfox!
It has something to do with how WordPress is calling the hook I need to make it work. I’m actively looking for a solution but so far none has presented itself.
It sounds like you turned on “hide backend.” By default (assuming you didn’t change it) you can access your admin page at /admin or /login.
Ah ha. Now I follow. Do you have any other plugins active that might be looking at wp-config?
Take a look at the logs and it will show all the 404 errors.
As for 403s, I had the same issue with CloudFlare (as well as a few others) and have stopped using the product. I’m afraid I cannot give you any more than that to go on.
Glad you found it. And you’re welcome. I only can check these forums about once a day but it does help.
Cheers!