ochado

I had this same problem, mostly likely because my shared hosting doesn’t give me enough RAM for it to work. (The plugin really should warn us about this! Anyway, that’s my only complaint against this otherwise awesome plugin.)

Based on Handoko’s comments above, I did the following focused change to get back into my site. Before I begin, I note that I use Online Backup for WordPress to make daily backups, so I had a safe fallback in case this hack didn’t work. I tried this just so that I could avoid reinstalling my entire site, and it happened to work for me:

1. I went to phpMyAdmin in my web host to enter into the WordPress database.
2. I located the xxxxx_options table. (Handoko said “wp_options”, but if you changed the database prefix like Better WordPress Security recommends, it will start with something other than “wp_”.)
3. In the xxxxx_options table, I located the row that with option_name=bit51_bwps (not to be confused with bit51_bwps_data). I clicked the edit (pencil) icon.
4. In the lengthy text box for option_value, I identified this portion: <strong>s:14:"id_fileenabled";i:1;</strong>. I guess that this means something like “string of length 14 characters with value id_fileenabled, whose value is an integer with value 1”. This is just a guess based on the structure of option_value. I’m guessing that this is the option (1 for true) that enables the file write tracking that knocked my site out.
5. I changed i:1 to i:0, so that the substring then became <strong>s:14:"id_fileenabled";i:0;</strong>. Please note that the only change I made to option_value was to change that single 1 to a 0; I left everything else intact.
6. I then saved my change (“Execute” button, with the “Save” option selected).

Boom! I typed in my site URL and my site was up again and I could login with no problem. However, all the Better WordPress Security settings were completely reinitialized, and I had to completely reconfigure it. (Only exceptions were fundamental changes I had made from the beginning, like changing the database prefix and content folder directory name–these major site changes remained intact.)

I hope this works for some other people as well.