CJM1504

Well if you are having the same problem that I was its a three line thing.
This is a CORRECT example I just pulled from mine.

SetEnvIF REMOTE_ADDR “^1\.36\.191\.253$” DenyAccess
SetEnvIF X-FORWARDED-FOR “^1\.36\.191\.253$” DenyAccess
SetEnvIF X-CLUSTER-CLIENT-IP “^1\.36\.191\.253$” DenyAccess

This is roughly what it looked like BROKEN (not 100 percent sure where it was cut off. But kind of remember a trailing quotation mark).

^1\.36\.191\.253$” DenyAccess
SetEnvIF X-FORWARDED-FOR “^1\.36\.191\.253$” DenyAccess
SetEnvIF X-CLUSTER-CLIENT-IP “^1\.36\.191\.253$” DenyAccess

What I would say is enable the plugin, see if it breaks the site.
IF it breaks you site
look at the .htaccess file and see if you can see any issues like the one posted above.
IF you find an issue I would say just remove that line plus the other two lines.

But it might not be the same problem at which case I would say turn off the plugin replace the htaccess file like you have been and roll with out the plugin.

Hey Guys,

I was heading over here to post about a possible feature request and saw this.

I had the same thing happen to me but was able to see the problem in the .htaccess file and correct it. Long story short I saw that one SetEnvIF DenyAccess statement was botched. Missing up to the RegEx IP part. Not sure were exactly as I just deleted it and blam site was back up.

BUT as a heads up the the Better WordPress Security guys after looking at a few of the other .htaccess files I am noticing that some of the rules being added are landing outside of the
# BEGIN Better WP Security
# END Better WP Security
comments. This happened on the site that went down as well. With out knowing to much and looking at the code I would guess what ever is parsing the .htaccess file might have a bug…